Priyank.Jain2 Posted January 31, 2018 Share Posted January 31, 2018 (edited) I am trying to build Unigine 2.6.1 using scons and getting following error. $ python build.py [ Engine: release build, 64 bit] building main app... executing command: scons_x64 debug=0 simd=sse2 vs_toolset=v141 jobs=all --warn=no-no-parallel-support --warn=no-missing-sconscript -Q -u . ********************************************************************** ** Visual Studio 2017 Developer Command Prompt v15.5.3 ** Copyright (c) 2017 Microsoft Corporation ********************************************************************** [vcvarsall.bat] Environment initialized for: 'x86_x64' Build time: 6.89 seconds. scons: *** No SConstruct file found. File "C:\install\Python27\scons-2.5.1\SCons\Script\Main.py", line 912, in _main Build FAILED! I am pretty sure that my environment is set correctly (including SCONSFLAGS) since I am able to build Unigine 2.3.1 and 2.5.1 using scons Is there anything obvious I am missing?) Edited January 31, 2018 by Priyank.Jain2 Link to comment
morbid Posted February 1, 2018 Share Posted February 1, 2018 Hi, May I ask you to check this: Isn't SConstruct really missing? Haven't you moved build.py? Which SDK edition is this? Pro or Sim? How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
Priyank.Jain2 Posted February 1, 2018 Author Share Posted February 1, 2018 Isn't SConstruct really missing? - No it is present at <sdk>\professional_windows_2.6.1_src\source Haven't you moved build.py? - No its still at <sdk>\professional_windows_2.6.1_src\utils Which SDK edition is this? Pro or Sim? Pro Link to comment
morbid Posted February 1, 2018 Share Posted February 1, 2018 Okay, we've found a problem with VS 2017 compatibility. You can try to build with --vs v120 if you have Visual Studio 2013 installed or --vs v140 for Visual Studio 2015. We need some time to fix this for VS 2017. How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
Priyank.Jain2 Posted February 1, 2018 Author Share Posted February 1, 2018 Yes that worked for me. Hope to get v141 working in next update. Link to comment
Priyank.Jain2 Posted February 2, 2018 Author Share Posted February 2, 2018 (edited) Hi Morbid, I have also observed that the output directory has been changed for the plugins and other libraries It use to be at $(ProjectDir)..\..\..\..\lib\ till 2.3.1 and now changed to $(ProjectDir)..\..\..\..\bin\ is there any specific reason to this? Edited February 2, 2018 by Priyank.Jain2 Link to comment
morbid Posted February 2, 2018 Share Posted February 2, 2018 lib folder is used for libraries to link with, bin is for dll and applications. Are you experiencing some troubles with it? How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
Priyank.Jain2 Posted February 2, 2018 Author Share Posted February 2, 2018 No. Just few changes need to be done in our build system. I am sure this will remain consistent now on. Link to comment
silent Posted February 28, 2018 Share Posted February 28, 2018 Hi Priyank, In the upcoming UNIGINE 2.7 SDK you will be able to use v141 toolset with Scons 3.x installed. We also moved build.py script from utils to source dir. Thanks! How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
Recommended Posts