We're experiencing some pain using the keyword install with native
build targets in 1.1 and 1.2.
When we leave "install" out, the targets build properly. When we use
"install", the builds fail. Operations appear to happen in the wrong
order, the process attempts to copy files that don't yet exist. The
paths generated by the build process appear to contain typos, in
that they are different from the paths generated using classic
targets. Classic uses blahblah/@executable_path, native uses
Our workaround is to not adopt to native build targets. We've been
using the classic targets, and wanted to switch to the native
targets to get some build speed.
The question I didn't ask in the original note is: have people
experienced a problem using "install" with native targets, does it
just work for you, or are you not using either install or native