>> Now I can trace PRG level calls in HBIDE with -D__HB_DEBUG__ define >> which in turn invokes hb_TraceString( [x,,,,] ) which in turn executes >> hb_tr_trace( HB_TR_ALWAYS,.. ). >> But still I cannot capture HBQT HB_TRACE( HB_TR_DEBUG, ... ) calls. >> HBQT compiles and shows up this in log: >> gcc -I. -I../../../../../include -Wall -W -O3 -fomit-frame-pointer >> -march=i586 -mtune=pentiumpro -Ic:\Qt\2009.03\qt\include >> -Ic:\Qt\2009.03\qt\include/QtCore -Ic:\Qt\2009.03\qt\include/QtGui >> -Ic:\Qt\2009.03\qt\include/QtNetwork -D__HB_WINDEBUG__ -D__HB_DEBUG__ >> -DHB_FM_STATISTICS -DHB_TR_LEVEL_DEBUG -ohbqt_destruct.o -c >> ../../../hbqt_destruct.cpp > > I have no idea what __HB_WINDEBUG__ does. As I can see it's not used at all. > __HB_DEBUG__ is you own macro used in hbqt.ch to disable HBQT_DEBUG() debug > messages in .prg code so it does not have to be passed to compile C code. > Remove both from your HB_USER_CFLAG settings.
__HB_WINDEBUG__ does nothing anymore. It was a temp solution and has been removed last week. It's superceded by HB_TR_WINOUT envvar. (these steps were documented in ChangeLog, for interested parties, most importantly Pritpal) Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
