List Info

Thread: bridges: building more directories in source/cpp_uno/...




bridges: building more directories in source/cpp_uno/...
user name
2007-03-31 04:33:38
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: mac-unsubscribeporting.openoffice.org
For additional commands, e-mail: mac-helpporting.openoffice.org


Re: bridges: building more directories in source/cpp_uno/...
user name
2007-03-31 06:21:15
Hi Pavel,

Pavel Janík a écrit :
> Hi,
> I'm working on universal binaries for Mac OS X and have
an  interesting 
> problem to solve 
> Bridges contain directories like

[...cut...]

> I extended it to contain
> bridges/source/cpp_uno/gcc3_macosx_universal

ok

> as well. This directory is built *after* first two dirs
mentioned  above 

Looking at your patches, and If I'm not wrong :

- ppc makefile is used, and libgcc3_*ppc.dylib is created
- intel makefile is used and libgcc3_*intel.dylib is
created

last, universal is used, and lipo does the final lib.


> and creates universal binary by combining the output
from these  
> directories.

ok


> It works, sort of 
> The problem is that intel dir contains:

[..cut..]


> So these three files are "shared".

Which size are these files ?

I'm not sure this is a good idea not to rename them. e.g.
for some 
reason rebuild the bridge, how know which one was the last (
ppc or i386 
? )


> My goal is to not change the name of these files, I do
not  care about 
> parallel build issues right now.

ok

  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

if you really don't want to rename slo files, this is the
moost simple.

> I simply feel that renaming is the proper solution
here,


Me too. I'd better imagine .o created with different names
(one 
containing i386 and the other ppc in it), and create
separate libs*.

If this build is possible ( no idea) , no more confusion for
the collect 
/ linking every lib, and no need to touch /delete .obj
files.

Last : parallel build becomes safer.


> but is there  
> any other solution available?

Sorry, no idea



Reagards,
Eric


------------------------------------------------------------
---------
To unsubscribe, e-mail: mac-unsubscribeporting.openoffice.org
For additional commands, e-mail: mac-helpporting.openoffice.org


Re: bridges: building more directories in source/cpp_uno/...
user name
2007-03-31 16:03:46
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 <Paveljanik.cz> 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: mac-unsubscribeporting.openoffice.org
> For additional commands, e-mail: mac-helpporting.openoffice.org
>
>


-- 
Mox on G
[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )