ACTION build setting
ACTION build setting
- Subject: ACTION build setting
- From: Jean-Denis MUYS <email@hidden>
- Date: Thu, 20 Sep 2012 10:04:44 +0000
- Thread-topic: ACTION build setting
Hi,
The Xcode documentation says that the ACTION build setting is controlled by Xcode's Product menu (and is an argument to xcodebuild). The only part of that menu that mentions "Action" is "Perform Action" which contains Run Without Building, Test Without Building, and Profile Without Building.
On the other hand, the documentation lists the possible values for the ACTION build setting:
- build
- clean
- install
- installhdrs
- installsrc
I can't reconcile the two. So is the documentation out of date, or incorrect? Or is Xcode incomplete?
I am currently interested in how to specify where an Xcode project building a static library for iOS should deposit the built library for use by other projects. My current idea is to have the library root directory and the different client application root directories to be in the same common "root" directory, and to make the library project install the library in that same root directory. The client apps would then refer to that library as a file reference (with the path "../libxxxlib.a).
The idea is that all projects would have their own git repositories and the libxxxlib.a file would not be under revision, and that all apps would refer to the same file. Updating the library once would update it for all apps. The App developers would not have to care about the library management.
The libxxxlib.a file is over 600 MB and takes a very long time to build, and it would be wasteful and useless to duplicate it in every App's directories. Putting it in the root directory means dependencies are limited to that root directory.
I have started exploring Xcode setting regarding installation, starting with INSTALL_PATH which is set to /usr/local/lib for the library (Xcode default). untangling the web of related settings leads me to believe this is never used within Xcode 4, since the install ACTION cannot be invoked.
I also had another look at schemes, which seem to contain what I find very similar to those ACTIONs (Build, Run, Test, Profile, Analyze, Archive), but not quite identical. This list is fixed however, and it doesn't seem possible to have an "Install" ACTION in that list.
Did I miss anything? What would be the best way to achieve what I am trying to achieve? I tend to think that I will need to alter the build ACTION that Xcode usually invokes to install my library in the root directory…
Any light shed on the that would be helpful. I feel a bit confused.
Thanks,
Jean-Denis
[Logo Kleegroup]
Klee Group is a great place to work – Il fait bon travailler à Klee Group
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden