Re: Custom build rule always rebuilding
Re: Custom build rule always rebuilding
- Subject: Re: Custom build rule always rebuilding
- From: Mark Lentczner <email@hidden>
- Date: Tue, 7 Mar 2006 09:25:15 -0800
On Mar 7, 2006, at 8:48 AM, James Bucanek wrote:
$(INPUT_FILE_BASE).y.h
not
$(INPUT_FILE_BASE).h
Good catch! Thanks. That partially cleared up the problem: On
single architecture builds, this made it work perfectly.
However, on universal builds it didn't, still yacc'ing twice and
compiling twice on every build.
But it gave me an idea: Make the derived files be architecture
dependent (is this what the normal yacc rule does?). So now the yacc
rule looks like:
-- Yacc source files using Script --
Process: Yacc source files
using: Custom script:
mkdir -p "${DERIVED_FILES_DIR}/${CURRENT_ARCH}"
/usr/bin/yacc -d -o "${DERIVED_FILES_DIR}/${CURRENT_ARCH}/$
{INPUT_FILE_BASE}.y.cpp" "${INPUT_FILE_PATH}"
with output files:
$(DERIVED_FILES_DIR)/${CURRENT_ARCH}/$(INPUT_FILE_BASE).y.cpp
$(DERIVED_FILES_DIR)/${CURRENT_ARCH}/$(INPUT_FILE_BASE).y.h
Works like a charm....
NOW the only problem is that the "CreateUniversalBinary" step runs
every time, even if there is nothing to do:
Checking Dependencies
CreateUniversalBinary ...
Is that normal? This is a static library.
- Mark
_______________________________________________
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