Re: ACTION build setting
Re: ACTION build setting
- Subject: Re: ACTION build setting
- From: Fritz Anderson <email@hidden>
- Date: Thu, 20 Sep 2012 10:26:05 -0500
(Answered in Mail, I have no recent experience, so this is an other "here's what I'd try next" answer.)
On 20 Sep 2012, at 5:04 AM, Jean-Denis MUYS <email@hidden> wrote:
> 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?
"Action," in the sense of "a build context within an Xcode 4 scheme," is a different concept from ${ACTION}, which had been an argument to make-based builds going back to ProjectBuilder. The two can't be reconciled, because they're not the same.
> 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.
See if you can put all your projects in a single workspace. Build products get a common derived-products directory, and cross-project references should Just Work. This may elicit a hollow laugh from some readers.
> 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.
Type "install" in the search field of the Build Settings tab of the Target editor. (A build-configuration file would be your friend here.) Examine each with Quick Help (first tab in the Inspector area), and see if that helps you. I'm particularly intrigued with turning DEPLOYMENT_LOCATION on.
However, I seem to remember you can't get that kind of installation from the Xcode IDE (sorry, haven't tried). You may have to resort to "xcodebuild… install" from the command line.
— F
--
Fritz Anderson -- Xcode 4 Unleashed: 4.5 supplement in the works -- <http://x4u.manoverboard.org/>
_______________________________________________
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