On Wednesday 31 of October 2012, Norbert Thiebaud wrote:
On Wed, Oct 31, 2012 at 8:34 AM, Lubos Lunak <l.lunak@suse.cz> wrote:
I'd prefer to not bring it back because of a special use case that's
already easily doable as it is.
Well tinderbox works nicely and easily with an autogen.lastrun
associated with a given profile...
messing with env variable is not as neat and is just a pain when
managing many of these profile...
what is the harm of --enable-symbol ?
./configure --enable-symbol
./configure CXXFLAGS='-Os -g'
Where's the difference in that?
note: I think the one that should go is dbgutil...
--enable-symbol => release build but with symbols
--enable-debug => debug build (with symbol of course)
extra feature (dbg-util) => --enable-debug + runtime trigger to
activate the 'special' stuff
How exactly do you envision a runtime trigger that activates binary
incompatibility? Because that's exactly what makes dbgutil different from
debug.
--
Lubos Lunak
l.lunak@suse.cz
Context
- Re: ENABLE_SYMBOLS=true does nothing (continued)
Re: ENABLE_SYMBOLS=true does nothing · David Ostrovsky
CPPUNIT road map, recent changes etc. · John McCabe
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.