Re: Mac OS X: Building SRC680m108 - are any patches necessary for a successful build?

Eric,

is the following problem (mentioned once by you) fixed meanwhile?

"And in the end instsetoo_native won't pack OOo because OS X cp
doesn't know -ua as arguments.
As a workaround I took what Terry Teague wrote as a citate of
Patrick Luby in his answer to the fact that we now should use
gnucopy instead of OS X cp.

After line 185 I added:
.IF "$(OS)"=="MACOSX"
         $(GNUCOPY) -r $(MSIOFFICETEMPLATESOURCE)
$(MSIOFFICETEMPLATEDIR:d:d)
         $(GNUCOPY) -r $(MSILANGPACKTEMPLATESOURCE)
$(MSILANGPACKTEMPLATEDIR:d:d)
         .ELSE
and and .ENDIF in line 192.

I tried to use gnucopy installed via Darwinports but it failed.
Could be another bug in Darwinport just like the one with freetype.
I had no time for further investigation and so far the build is
fine with this hackaround."

Kind regards,
Tino


Eric Hoch wrote:
> Hi Tino, 
> Am Fri, 10 Jun 2005 10:52:05 +0200, schrieb Eric Hoch:
> 
>>Hi Tino, 
>>Am Fri, 10 Jun 2005 09:29:34 +0200, schrieb Tino Rachui - Sun 
>>Germany - Development - Software Engineer:
>>
>>> Hi!
>>> 
>>> I would like to build a SRC680m108 over the weekend.
>>> Can I just checkout out start building or do I need
>>> to apply any patches beforehand (e.g. that of
>>> CWS ause031) in order to succeed?
>>
>>Yes. Without the ause03 patch OOo build of m108 crashes :-)
>>
>>Sinc cws gslpatches is in 108 you won't need it any longer.  
>>
>>You can test the metapackage script out of IZ 42998 
>><http://www.openoffice.org/issues/show_bug.cgi?id=42998> and the 
>>patch maho attached to IZ 50455 
>><http://qa.openoffice.org/issues/show_bug.cgi?id=50455>. 
>>
>>Perhaps take a look at the Issue for the locales Eric B. mentioned 
>>in his list. 
>>
>>But according to Rüdiger Timm. Wait for m109 to see what cws are 
>>included.
>>
>>I will also build m109 using Panther. 
> 
> 
> Additional Info: You should also try Florian's patches out of 
> IZ50016 and IZ50150. They solve some circular depencies for OOo 
> libraries that according to Florian weren't fixed in total by older 
> patches. With these two patches the Macro Security Dialogue is up 
> and running again. 
> 
> Regards, 
> Eric Hoch
>