Re: Fwd: Re: has overriding C++ compiler paths and names changed with Python 3.x?
Damien <[email protected]>
| Newsgroups | gmane.comp.programming.tools.scons.user |
|---|---|
| Message-ID | <[email protected]> |
It's probably us and our build setup. We build for Win & Lin, 32 & 64, Intel, AMD & ARM, all C++/Fortran maths and algorithms, custom optimisation flags everywhere, and a partridge in a pear tree. Damien On 1/18/2019 2:03 PM, Eric Fahlgren wrote: > I just upgraded from 3.0.1 and don't see this problem. Using VS 2017, > Win 10, Py 3.7, finds the compiler just fine, although my Visual > Studio hasn't been updated for 5-6 months... > > (I did hit a catch on the renaming of Scripts/scons.py to just > Scripts/scons, though.) > > On Fri, Jan 18, 2019 at 9:29 AM Bill Deegan <[email protected] > <mailto:[email protected]>> wrote: > > Damien, > > O.k. Look out for 3.0.4 coming in the next week.. > > On Thu, Jan 17, 2019 at 9:23 PM Damien <[email protected] > <mailto:[email protected]>> wrote: > > I meant to send this to the list earlier instead of just Mats. > > -------- Forwarded Message -------- > Subject: Re: [Scons-users] has overriding C++ compiler paths > and names changed with Python 3.x? > Date: Thu, 17 Jan 2019 19:35:53 -0700 > From: Damien <[email protected]> <mailto:[email protected]> > To: Mats Wichmann <[email protected]> <mailto:[email protected]> > > > > OK, the 3.0.1 release works and the tip of Master also works. > 3.0.3 doesn't work. > > Damien > > On 1/17/2019 5:16 PM, Mats Wichmann wrote: >> On 1/17/19 4:36 PM, Damien wrote: >>> Hi all, >>> >>> For probably ten years we've run a custom build setup, >>> overriding SCons >>> default behaviour for compiler selection, library flags etc >>> depending on >>> what OS we're on and what compiler versions we need to use. >>> We've been >>> on 3.0.1 with Python 2.7 for a year now. We're just setting >>> up a CI/QC >>> server with 3.0.3 and Python 3.7.2. SCons is now >>> complaining that there >>> are no C++ compilers installed, even though we have set the path >>> explicitly. This is with Visual Studio 2017, v15.9.5, it >>> just came out >>> a few days ago. >>> >>> We now get the missing compiler message: scons: warning: No >>> version of >>> Visual Studio compiler found - C/C++ compilers most likely >>> not set >>> correctly >>> >>> In the SCons environment, we set the following in a .py file >>> that's >>> called by the SConscript from SConstruct: >>> >>> cxxcompilerpath = ["C:/Program Files (x86)/Microsoft Visual >>> Studio/2017/Community/VC/Tools/MSVC/14.16.27023/bin/Hostx64/x64"] >>> env.PrependENVPath('PATH', cxxcompilerpath) >>> env['CXX'] = 'cl.exe' >>> >>> That cxxcompilerpath exists and cl.exe is there. This has >>> worked for >>> years for us. >>> >>> We get the standard command prompt "can't find it" message: >>> >>> 'cl.exe' is not recognized as an internal or external command, >>> operable program or batch file. >>> >>> SCons was installed with "python setup.py install", not with >>> pip. >>> >>> Any suggestions? >> can you try the current git head possibly? there's an ongoing >> wrestling >> match with this stuff, and more changes landed after 3.0.3 >> dropped. >> >> > > _______________________________________________ > Scons-users mailing list > [email protected] <mailto:[email protected]> > https://pairlist4.pair.net/mailman/listinfo/scons-users > > _______________________________________________ > Scons-users mailing list > [email protected] <mailto:[email protected]> > https://pairlist4.pair.net/mailman/listinfo/scons-users > > > _______________________________________________ > Scons-users mailing list > [email protected] > https://pairlist4.pair.net/mailman/listinfo/scons-users _______________________________________________ Scons-users mailing list [email protected] https://pairlist4.pair.net/mailman/listinfo/scons-users