On Wednesday 21 of September 2011, Bjoern Michaelsen wrote:
> On Wed, 21 Sep 2011 12:55:44 +0200
>
> Lubos Lunak wrote:
> > You forgot Qt4/KDE4. LO does not use STL with it, so this is just to
> > show that it's not so trivial to check if there's a potential
> > problem. And I seriously doubt the
On Wed, 21 Sep 2011 12:55:44 +0200
Lubos Lunak wrote:
> You forgot Qt4/KDE4. LO does not use STL with it, so this is just to
> show that it's not so trivial to check if there's a potential
> problem. And I seriously doubt there's a good way how to check for
> this automatically, so the only way
On Thursday 15 of September 2011, Michael Stahl wrote:
> On 15.09.2011 16:34, Caolán McNamara wrote:
> > On Thu, 2011-09-15 at 14:34 +0200, Michael Stahl wrote:
> >> of course what also needs to be prevented is linking against system
> >> libraries that expose STL in their interface; a quick search
Dear All,
> * graphite: apparently built with dmake, so a problem only if from system
graphite used to require STL, but with 3.4 and gr2, no such requirement or
exposure remains. Graphite is built using dmake, but is a relatively simple
library to package and could easily be converted to anothe
On 15.09.2011 16:34, Caolán McNamara wrote:
> On Thu, 2011-09-15 at 14:34 +0200, Michael Stahl wrote:
>> of course what also needs to be prevented is linking against system
>> libraries that expose STL in their interface; a quick search found me
>> cppunit and graphite; the mozilla/nss stuff doesn'
> For the internal cppunit and graphite probably need to pass
> -D_GLIBCXX_DEBUG into *their* build systems as well, no ?
On the Windows side, the internal cppunit and graphite makefiles use
dmake to build them, so there the -D_DEBUG in dbgutil mode does get
used. Not necessarily in other of the 3
On Thu, 2011-09-15 at 14:34 +0200, Michael Stahl wrote:
> of course what also needs to be prevented is linking against system
> libraries that expose STL in their interface; a quick search found me
> cppunit and graphite; the mozilla/nss stuff doesn't seem to expose STL.
This is basically the scen
On Thursday 15 of September 2011, Michael Stahl wrote:
> On 14.09.2011 20:50, Tor Lillqvist wrote:
> >> but currently LO doesn't seem to use it (couldn't find
> >> -D_GLIBCXX_DEBUG); why is that?
> >
> > We tried, but we ran into so many problems when code compiled with
> > that without that were m
> hmmm... but why hook this into --enable-debug, and not --enable-dbgutil?
Good question...
> AFAIK --enable-debug just enables symbols, and is otherwise intended to be
> compatible with an ordinary build.
We also have --enable-symbols ;) I don't know why we need that
separately, and what the -g
On 14.09.2011 20:50, Tor Lillqvist wrote:
>> but currently LO doesn't seem to use it (couldn't find -D_GLIBCXX_DEBUG);
>> why is that?
>
> We tried, but we ran into so many problems when code compiled with
> that without that were mixed (accidentally/unintentionally) that we
> gave up.
hmmm... g
10 matches
Mail list logo
