On Wed, 16 Sep 2009, Viktor Szakáts wrote: hi,
> hbmk2 doesn't understand HB_BUILD_MODE envvar. You have to it was just a shot in the dark :) > use '-cpp' switch. In fact there are quite some GNU Make this works, thanks. in this case, hbmk2 invokes g++, which is the right thing to do. > envvars which aren't implemented in hbmk2, and honestly I'd > rather delete existing ones first to clean off some time > waste trying to keep these in sync, and also to clean away > often seen confusion when envvar leftovers change hbmk2 > behavior in hard-to-detect and unwanted way. please do. > Dunno how this breaks general assumption from such cmdline > tools, but I'm 100% in favor of cmdline switches. Opinions agreed. > [ BTW, HBMK2_OPTION envvar could be added, which would > accept simple cmdline options as is. ] this sounds like a good idea, as a convenience. in my opinion, this shouldn't in any way affect anything else talked about above and below. > > explicitly specify HB_USER_LDFLAGS=-lstdc++, then it works (i reckon > > gcc does this automatically when called as g++, and needs to be given > > if called as gcc). > > If we can define the rules when to include this lib I can add > it to hbmk2. First confusion is what is the difference between > supc++ and stdc++ ? mingw/win requires supc++ when linking hbqt. i would rather say that if harbour was built with cpp mode, then hbmk2 should call g++ (CXX) instead gcc (CC) automatically. "manually" messing with this seems counterintuitive, no? this i believe also would take care of stdc++ vs supc++ (no idea what the difference is), libCrun on sunpro, and other c++ support libs other compilers might have. i think. -- [-] mkdir /nonexistent _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
