I have a Java project that includes a language parser class generated
JavaCC. My builds begin with a custom shell script that checks the
modification time of the grammar file and invokes JavaCC as needed. The
resulting parser file overwrites the previous version on disk, and it
then compiled along with the rest of the application.
This all worked in ProjectBuilder. In Xcode, however, the builds ignore
the newly created parser Java source file and try to compile the
previous version. This behavior might make sense if Xcode uses aliases
in its source file list, while ProjectBuilder used symbolic links.
Neither is true, so that's not it.
Is there something simple I can add to my shell script or to my Xcode
project that will cause the build to get the new parser file each time?
You can make the input file a dependency of the shell script, by
entering its name (or partial path from the project folder) into the
"Input Files" list in the Run Script build phase, and also make the
output file a member of the Compile Sources build phase.
Providing a build transcript of what Xcode is actually doing, both for
your Run Script build phase and for the Compile Sources build phase,
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