Re: 2 Questions about custom (script) build rules
Re: 2 Questions about custom (script) build rules
- Subject: Re: 2 Questions about custom (script) build rules
- From: Chris Hanson <email@hidden>
- Date: Sun, 30 Oct 2016 12:23:25 -0700
On Oct 26, 2016, at 4:17 PM, Motti Shneor <email@hidden> wrote:
1. Creating a framework, I would like to make the generated headers (.pb.h files) public - so they’re automatically copied to the framework’s headers directory. Unfortunately, I only found a way to set the visibility scope of header files (Pritave/Project/Public) via Xcode UI, when they are manually added to the project, and I see their references. Is there a decent way to do this?
You could add file references to the generated files—pointing to the location at which they’re generated, via a Relative to Build Products reference (since both Build Products and Derived Files are part of Derived Data)—to your project, and then add those references to your Copy Headers phase which would let you set them as public/private/project. 2. Is it possible to setup my rule to generate code outside the ${DERIVED_FILE_DIR}? in such case, will Xcode continue to compile the generated sources? My attempts have failed so far.
As far as I recall, Xcode shouldn’t care where the generated code is produced; as long as the path to the generated file is correct in the Output Files section of the rule, and it’s of a type Xcode knows how to build, Xcode should further build it.
-- Chris
|
_______________________________________________
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