Hi Pavel,
Great that you continue with the universal build stuff :)
I'd also vote for renaming the SLOFILES to processor specific ones, either
1) $(SLO)$/$(ARCH)$/*.obj
or
2) $(SLO)$/except-$(ARCH).obj, $(SLO)$/cpp2uno-$(ARCH).obj, etc
where ARCH=powerpc or intel
At least to me it seems all the other possibilities would end up being
hacky and would make the process more obscure for other developers.
Mox
On 3/31/07, Pavel Janík <[EMAIL PROTECTED]> wrote:
Hi,
I'm working on universal binaries for Mac OS X and have an
interesting problem to solve ;-)
Bridges contain directories like
bridges/source/cpp_uno/gcc3_macosx_intel
bridges/source/cpp_uno/gcc3_macosx_powerpc
etc.
I extended it to contain
bridges/source/cpp_uno/gcc3_macosx_universal
as well. This directory is built *after* first two dirs mentioned
above and creates universal binary by combining the output from these
directories.
It works, sort of ;-)
The problem is that intel dir contains:
SLOFILES= \
$(SLO)$/except.obj \
$(SLO)$/cpp2uno.obj \
$(SLO)$/uno2cpp.obj \
$(SLO)$/call.obj
and powerpc:
SLOFILES= \
$(SLO)$/except.obj \
$(SLO)$/cpp2uno.obj \
$(SLO)$/uno2cpp.obj
So these three files are "shared".
This brings some interesting issues like parallel build issues,
ordering issues (if the Intel is built first, PPC files are not
built) etc. Is there any way to solve this issue *without* renaming
the files? My goal is to not change the name of these files, I do not
care about parallel build issues right now. Good enouhg (for now) fix
for me would be one of:
- remove $SLOFILES after the TARGET is created
- touch source files *before* the TARGET is created
Or?
I simply feel that renaming is the proper solution here, but is there
any other solution available?
--
Pavel Janík
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Mox on G
