Re: Correct way to compile and link derived sources?
Re: Correct way to compile and link derived sources?
- Subject: Re: Correct way to compile and link derived sources?
- From: Commodore 64 <email@hidden>
- Date: Fri, 14 Sep 2012 17:37:13 -0700
Click on the blue Project, then select your target, and bring up the Build Phases tab. Expand the Compile Sources section, click the + button and specify your .rl file there.
HTH
On Sep 14, 2012, at 12:10 AM, Crispin Bennett <email@hidden> wrote:
> I have a build rule set up for files with a .rl extension, thus:
>
> /usr/local/bin/ragel $INPUT_FILE_PATH -o $DERIVED_FILES_DIR/$INPUT_FILE_BASE.c
>
> What's the recommended way to compile and link the derived file? I confess I just assumed that the 'Output Files' part of the build rule configuration would be for this purpose (ie. output files would automatically be built as part of the project). But it seems not : linking fails if I do try to call on any of the code in the derived file.
>
> For now I've just added the derived file directly to the project, which works OK as a quick hack for the sake of testing in the Simulator, but obviously isn't a viable solution.
>
>
>
> _______________________________________________
> 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
_______________________________________________
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