Re: Build break MacOS X - SRC680_m95

Hi Sergio, 
Am Mon, 2 May 2005 23:47:18 -1000, schrieb Sergio Trejo:
> Hello Eric,
> 
> On 5/2/05, Eric Hoch <[email protected]> wrote:
>>  Hi Sergio,
>>  Am Mon, 2 May 2005 22:40:40 -1000, schrieb Sergio Trejo:
>>>  On 5/1/05, Eric Hoch <[email protected]> wrote:
>>>>   Hi Sergio,
>>>>   Am Sun, 1 May 2005 06:17:13 -1000, schrieb Sergio Trejo:
>>>  Hi Eric H.,
>>> 
>>>  Just wanted to let you and others know that Mr. NAKATA Maho's patches
>>>  via FTP do not include m95, so I am going to try out m96 in a few
>>>  moments.
>>  
>>  O.K.
>>  
>>>  I wonder, are Maho's patches to be used in addition to all of
>>>  the other patches (including from your iDisk for 680 m90)?
>>> 
>>>  Therefore, to build 680 m96 the patches to apply are:
>>> 
>>>  Maho's  + Eric H's from his iDisk 680m90 + Florian Heckl's 
>>> Mozilla patches?
>>  
>>  This is necesary if you build with Darwinports gtk2 and don't want
>>  to compile Mozilla yourself.
>>>  Or just:
>>> 
>>>  Maho's + Florian Heckl's Mozilla patches?
>>  
>>  This is necessary if you have gtk2 via fink or build it yourself
>>  and don't want to compile Mozilla yourself.
> 
> Actually, I have both gtk2 and Mozilla 1.7.6 already installed and
> working fine via DarwinPorts. However, I do not mind compiling Mozilla
> again for the benefit of OOo 1.9 m96 if that is what it takes.

I wrote it before. OOo ignores Darwinport Mozilla 1.7.6. It will 
fail if you use it. 

If you don't want to compile mozilla simply use my patch package 
and the moz_deliver patch. Download Florian's pre build Moz 
packages and you're done. 

> Per your other message, I indeed would like SSL capability that the
> Mozilla compile gives us.
> 
>>  I guess I will split up my patch package into one package for the
>>  Darwinport freetype problem and one for using pre-compiled Mozilla
>>  libs.
>>  Any ideas how to make things clearer in my build instructions. I
>>  hoped it not to be that confusing but it looks like it is.
> 
> I think your build instructions are fine. I was just a little bit
> unsure about how Maho's packages are to be integrated becuase his
> packages are only for m96+ and since your build instructions are for
> m90

I took m90 as an example. You can use them for any milestone higher 
than m90. I mentioned it as often as I could that these build 
instructions are made for m90 and higher. It's just the fact that I 
cannot update the buildinstructions everytime a new milestone is 
out. 

> I wasn't sure if your iDisk patches applied toward > m90 such as
> and including m95, m96, etc.
> 
> For example, from your m90 patches, we have:
> 
> build/freetype2_test/freetype-2.1.9.patch
> 
> Yet, in the m96 build directory, I can not find:
> 
> --- misc/build/freetype-2.1.9/builds/unix/freetype-config.in
> 
> But there is this folder:
> 
> build/freetype/freetype-2.1.4.patch
> 
> and
> 
> build/freetype/download/freetype-2.1.4.tar.gz

Freetype 2.1.4 won't compile within OOo using Mac OS X. Therefore 
my freetype patch set replaces 2.1.4 with a complete set of patches 
and other needed stuff for 2.1.9 which compiles just fine using Mac 
OS X. 

> Thus, I presume that m96 can not use the freetype-2.1.9.patch from
> your iDisk for m90 since there is a version mismatch (2.14 v.s. 2.19)?

My patch includes a tar.gz archive of freetype2 2.1.9 and you 
replace the version 2.1.4 you checked out with the version 2.1.9 
that's in my patch package. See two sentences above 2.1.4 won't 
compile within OOo under MAc OS X. 

 
Mit freundlichen Grüßen
Eric Hoch

-- 
## Ansprechpartner Anwenderunterstützung, users-Mailingliste, MacOSX
## de.OpenOffice.org - Office für MacOS X, Linux, Solaris & Windows
## Openoffice.org - ich steck mit drin!