3.0.5 msvc path construction problem

"Joseph C. Brill" <[email protected]>
Newsgroups gmane.comp.programming.tools.scons.user
Message-ID <008601d4e49c$23cdada0$6b6908e0$@com>
SCons 3.0.5 adds additional paths to the ENV['PATH'] after the default MSVC
configuration as compared to SCons 3.0.4.

The following paths are added to the ENV['PATH'] after the msvc
configuration in SCons 3.0.5:
    C:\\ProgramData\\chocolatey\\bin;
    C:\\msys64;
    C:\\msys;
    C:\\cygwin64\\bin;
    C:\\cygwin\\bin;
    C:/Program Files\\Java\\jdk1.8.0_172\\bin;

The following paths are added to the ENV['PATH'] after the msvc
configuration in SCons 3.0.4:
    C:\\Program Files\\Java\\jdk1.8.0_172\\bin;

When configured from the command line using vcvarsall.bat, the JDK is not
added to the path.

In a build script, the mingw-w64 path is manually added to the end of the
environment path using AppendENVPath().  The build fails due to the
appearance of C:\cygwin\bin on the path in front of the desired mingw-64
path added from user space.  The failure is due to dlltool being called to
produce a 64-bit import library on a 32-bit system.  Evidently, the cygwin
dlltool does not support this (or is not configured correctly).

I don't believe that any of the chocolatey, mingw, cygwin, or JDK paths
should be added to the ENV['PATH'] for an msvc build.

Since I am not a java/jdk user, I never noticed the JDK being automatically
added to the path.

The above applies to MSVC 2005, 2008, 2010, 2012, 2013, and 2017.

Regards,
Joe

_______________________________________________
Scons-users mailing list
[email protected]
https://pairlist4.pair.net/mailman/listinfo/scons-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.