3 May
2012
3 May
'12
1:04 p.m.
On 05/03/2012 02:56 PM, David C. Rankin wrote:
On 05/03/2012 02:34 PM, /dev/ammo42 wrote:
What about the QMAKE variables. Is there any need to specify them as well in a
patch or something?
QMAKE_CFLAGS = -pipe -g -fvisibility=hidden -fvisibility-inlines-hidden
QMAKE_CFLAGS_DEPS = -M
QMAKE_CFLAGS_WARN_ON = -Wall -W
QMAKE_CFLAGS_WARN_OFF = -w
QMAKE_CFLAGS_RELEASE = -O2
QMAKE_CFLAGS_DEBUG = -O0
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
QMAKE_CFLAGS_SHLIB = -fPIC
QMAKE_CFLAGS_YACC = -Wno-unused -Wno-parentheses
QMAKE_CFLAGS_THREAD = -D_REENTRANT
QMAKE_CXX = g++
QMAKE_CXXFLAGS = $$QMAKE_CFLAGS
QMAKE_CXXFLAGS_DEPS = $$QMAKE_CFLAGS_DEPS
QMAKE_CXXFLAGS_WARN_ON = $$QMAKE_CFLAGS_WARN_ON
QMAKE_CXXFLAGS_WARN_OFF = $$QMAKE_CFLAGS_WARN_OFF
QMAKE_CXXFLAGS_RELEASE = $$QMAKE_CFLAGS_RELEASE
QMAKE_CXXFLAGS_DEBUG = $$QMAKE_CFLAGS_DEBUG
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
QMAKE_CXXFLAGS_SHLIB = $$QMAKE_CFLAGS_SHLIB
QMAKE_CXXFLAGS_YACC = $$QMAKE_CFLAGS_YACC
QMAKE_CXXFLAGS_THREAD = $$QMAKE_CFLAGS_THREAD
--
David C. Rankin, J.D.,P.E.
On Thu, 3 May 2012 21:26:50 +0200
"Mag. Dr. Nikolaus Klepp"<office(a)klepp.biz> wrote:
OK, got it CXXFLAGS="${CXXFLAGS} -g -01"
Any other tweaks yo can think of and I'll add them. Thanks.
>> > > > What's the trick for
tqt3?
> > >
> > > If you can mandate custom CXXFLAGS, just adding "-g" to them
should
> > > suffice.
>
> and turn any optimisation off :-)
According to the GCC manual pages -O1
implies -fomit-frame-pointer only
if it doesn't interfere with debugging, so it should be safe.
Also -fomit-frame-pointer can be reversed by -fno-omit-frame-pointer.
> >
> > nik
> >