Re: Re: More on "tools" module; on FreeBSD

Maho NAKATA <[email protected]> Sun, 23 Jan 2011 10:00:51 +0900 (JST)
Newsgroups gmane.comp.openoffice.devel.porting
Message-ID <[email protected]>
From: Michael Stahl <[email protected]>
Subject: [porting-dev] Re: More on "tools" module; on FreeBSD
Date: Mon, 17 Jan 2011 11:15:44 +0100

> On 16/01/2011 06:29, Takashi Ono wrote:
>> Hi Maho,
>> 
>> In message "Re: [porting-dev] More on "tools" module; on FreeBSD",
>> Maho NAKATA wrote...
>> 
>>  >where ../../solver/300/unxfbsdi.pro/workdir/Headers/Library/libcomphelpergcc3.so comes 
>> from?
>> 
>> The names of the libraries are defined in Reopsitory.mk and RepositoryFixes.mk in source 
>> root. I think you need some fix entries for FreeBSD in RepositoryFixes.mk.
> 
> yes, exactly.
> 
> the problem is that unfortunately there is significant creativity when it
> comes to library names in OOo.
> 
> gbuild needs to construct the file names of the library somehow.
> this is done by generic rules that e.g. append the 2/3-letter platform
> suffix and such.
> 
> in many cases this is sufficient, but there are quite a few exceptions.
> like comphelper, which is called libcomphelp4gcc3.so or something like
> that on linux, and something else on windows, for reasons nobody knows.
> 
> these exceptions are handled on a per-platform basis in RepositoryFixes.mk.
> if your platform is "just like linux", then you may be able to just re-use
> the linux stuff in that file.

yes, that's actually what I have been doing :-)
and in FreeBSD's case, just copy and paste from Linux is usually enough.

Thanks,
 Nakata Maho