# make install Mac arm64

**URL:** https://discourse.cmake.org/t/make-install-mac-arm64/13128
**Category:** Usage
**Created:** [December 5, 2024, 4:44am UTC](https://discourse.cmake.org/t/make-install-mac-arm64/13128 "2024-12-05T04:44:48Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![lindsayad](https://discourse.cmake.org/user_avatar/discourse.cmake.org/lindsayad/32/5171_2.png) [@lindsayad](https://discourse.cmake.org/u/lindsayad)
#### Post date: [December 5, 2024, 4:44am UTC](https://discourse.cmake.org/t/make-install-mac-arm64/13128/1 "2024-12-05T04:44:49Z")

</div>

What is current best practice for avoiding warnings about invalidation of code signatures due to install\_name\_tool modification of binaries when copying from build to install? I’ve found advice to add custom post build commands to codesign. I saw something within the past couple years about some special Xcode attribute at [Code Signing macOs application](https://discourse.cmake.org/t/code-signing-macos-application/7275). I cloned paraview and grepped for codesign hoping I might get some guidance there but got no hits. Any advice would be appreciated!
