incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Stahl <...@openoffice.org>
Subject Re: How to do with glibc-2.1.3 in AOOo?
Date Wed, 14 Sep 2011 15:43:18 GMT
On 14.09.2011 17:23, Pedro F. Giffuni wrote:
> Thanks Tor, this is all good to know!
> 
> --- On Wed, 9/14/11, Tor Lillqvist <tml@iki.fi>
> wrote: ....
>>> The question is why do we need
>> this? I would think
>>> all supported platforms have standard conformant C/C++ libs.
>> 
>> Yeah, but the code uses non-standard library functions, 
>> apparently.
> 
> Both of these appear to be standard (now?)

perhaps. but see below :)

>> See external/glibc/makefile.mk. Apparently what's needed is 
>> getopt()
> 
> In FreeBSD we were using an independent library in some ports to
> support getopt_long but the regular library now supports the GNU
> extensions. If it's needed it can be taken from there.

if it's not in a C standard at least 20 years old then usually MSVC
doesn't have it.

>>> In the same line of questioning, but not a license issue, why do
>>> we need STLport?
>> 
>> (In LibreOffice we don't use STLport any more on any platform.)
>> Your code presumably still relies on some STLport stuff on Windows.
>> Anyway, even if AOOo itself wouldn't use STLport itself, if you
>> want to be binary compatible with binary extensions, those might
>> rely on the OOo installation containing a STLport shared library so
>> you need to build and ship it.
>> 
> 
> I think we should just follow LO on this one. The STLport OOo carries
> is outdated and the latest versions in sourceforge (2008) are not
> very well maintained (broken on MacOS X and BSD, AFAICT).

only reason why OOo ships STLport is ABI compatibility
of the URE and for C++ UNO extensions.

we wanted to get rid of it for OOo 4.0 anyway.


Mime
View raw message