> > Harbour extensions: Yes > > CA-Clipper 5.2e undocumented: Yes > > CA-Clipper 5.2e strict compatibility: No > > CA-Clipper 5.3x compatible extensions: Yes > > Alaska Xbase++ compatible extensions: Yes > > CA-Visual Objects compatible extensions: No > > Multisoft Flagship compatible extensions: Yes > > Microsoft FoxPro compatible extensions: Yes > > dBase compatible extensions: No > > Object file generation support: No > > ANSI C usage: Non strict > > C++ mode: Off > > Compiler YACC debug mode: Off > > Memory tracing and statistics: Off > > Maximum symbol name length: 63 > > > > Is there a way to disable any of the above extensions without touching > > hbsetup.ch?
Ah OK. I think I got you. Each compiler has its own way to undef predefined constant. For example, in case of Borland Compiler, you can use one of these flags: -U"HB_EXTENSION" -U"HB_C52_UNDOC" -U"HB_COMPAT_C53" -U"HB_COMPAT_XPP" -U"HB_COMPAT_FLAGSHIP" -U"HB_COMPAT_FOXPRO" -U"HB_C52_STRICT" So in a clean build, just set an envar: SET CLIBFLAGS=-U"HB_COMPAT_C53" -> you are disabling CA Cl*pper 5.3 extension without touching hbsetup.ch Andi ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ xHarbour-developers mailing list xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers
