On Fri, 13 Mar 2009, Przemyslaw Czerpak wrote: Hi, > > Perhaps we would need a Harbour compiler switch to force to > > ignore all envvars (CLIPPER, HARBOUR, INCLUDE), named > > -noenv. This would be a safe way to create builds which are for > > sure okay and eliminating all these problems. > > Unfortunately it's not an option to clear INCLUDE envvar in > > make_gnu.bat, as it may be needed by some C compilers. > > Przemek, what do you think? > Probably it's the best solution. > Anyhow I would like to check include precedence in Clipper. > What has higher priority: INCLUDE envvar or -I compiler switch. > It's possible that we only have to fix it in Harbour compiler.
I've just check and clipper, harbour and hbpp gives higher priority to directories specified by -I command line option then for INCLUDE envvar so I do not see any way where INCLUDE envvar can change header files used to compile Harbour core code or I'm missing sth important in current build scripts. I think that we should exactly replicate the problem or it will return. Viktor can you make some tests in windows and set INCLUDE=C:\ echo #error Wrong std.ch file > C:\std.ch JF I would like to confirm that you resolved the problem only changing INCLUDE envvar without any other modifications. At this moment I see only one situation which could cause problems: Your local std.ch was in the current directory when you were building Harbour. best regards, Przemek _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
