Page 1 of 2

Trying to build SDK

Posted: Wed Oct 02, 2019 4:04 pm
by em3
After failing to build freeorion before, I decided to try and build SDK first. I have some problems. I apologise that some diagnostic messages are in Polish. I tried to force MSBuild, PowerShel et al to switch to invariant culture, but without success.

Python - no numpy:

Code: Select all

  notice: [python-cfg] Configuring python...
  notice: [python-cfg]   user-specified version: "2.7"
  notice: [python-cfg]   user-specified cmd-or-prefix: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python
  2.7"
  notice: [python-cfg]   user-specified includes: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/include/python2
  .7"
  notice: [python-cfg]   user-specified libraries: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/lib"
  notice: [python-cfg] Checking interpreter command "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python2.7
  "...
  notice: [python-cfg] running command 'C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python2.7 -c "from sys
   import *; print('version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s' % (version_info[0],version_in
  fo[1],platform,prefix,exec_prefix,executable))" 2>&1'
  notice: [python-cfg] ...requested configuration matched!
  notice: [python-cfg] Details of this Python configuration:
  notice: [python-cfg]   interpreter command: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python2.7"
  notice: [python-cfg]   include path: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/include/python2.7"
  notice: [python-cfg]   library path: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/lib"
  notice: [python-cfg]   DLL search path: "<empty>"
  notice: [python-cfg] Checking for NumPy...
  notice: [python-cfg] running command 'C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python2.7 -c "import s
  ys; sys.stderr = sys.stdout; import numpy; print(numpy.get_include())"'
  notice: [python-cfg] NumPy disabled. Reason:
  notice: [python-cfg]   C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python2.7 -c "import sys; sys.stderr
  = sys.stdout; import numpy; print(numpy.get_include())" aborted with
  notice: [python-cfg]   Traceback (most recent call last):
    File "<string>", line 1, in <module>
  ImportError: No module named numpy
The same problem was reported for Python 3.5.

No clang

Code: Select all

CUSTOMBUILD : warning : toolset clang-linux initialization: can not find tool clang++ [C:\Users\miron\Documents\Build\f
reeorion-sdk\boost.vcxproj]
CUSTOMBUILD : warning : initialized from C:\Users\miron\Documents\Build\freeorion-sdk\boost-config.jam:20 [C:\Users\mir
on\Documents\Build\freeorion-sdk\boost.vcxproj]
  '"clang++"' is not recognized as an internal or external command,
  operable program or batch file.
  notice: will use 'clang++' for clang-linux, condition <toolset>clang-linux
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/tools\clang-linux.jam:63: in clan
  g-linux.init
  *** argument error
  * rule clang.init-cxxstd-flags ( toolset : condition * : version )
  * called with: ( clang-linux : <toolset>clang-linux :  )
  * missing argument version
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/tools\clang.jam:54:see definition
   of rule 'clang.init-cxxstd-flags' being called
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/build\toolset.jam:44: in toolset.
  using
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/tools\clang.jam:33: in clang.init
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/build\toolset.jam:44: in toolset.
  using
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/build\project.jam:1104: in using
  C:\Users\miron\Documents\Build\freeorion-sdk\boost-config.jam:20: in modules.load
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src\build-system.jam:255: in load-con
  fig
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src\build-system.jam:449: in load-con
  figuration-files
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src\build-system.jam:607: in load
  C:\Users\miron\Documents\Build\freeorion-sdk\boost-prefix\src\boost\tools\build\src/kernel\modules.jam:295: in import
  C:\Users\miron\Documents\Build\freeorion-sdk\boost-prefix\src\boost\tools\build\src/kernel/bootstrap.jam:139: in boos
  t-build
  C:\Users\miron\Documents\Build\freeorion-sdk\boost-prefix\src\boost\boost-build.jam:17: in module scope
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(209
,5): error MSB6006: Polecenie "cmd.exe" zakończone przez kod 1. [C:\Users\miron\Documents\Build\freeorion-sdk\boost.vcx
proj]
Kompilowanie projektu "C:\Users\miron\Documents\Build\freeorion-sdk\boost.vcxproj" wykonane (domyślne elementy docelowe
) - NIEPOWODZENIE.
Does that mean I need to have clang installed (and in path)? https://github.com/freeorion/freeorion- ... /README.md does not mention this.

I'm using Visual Studio 2017 toolset.

Re: Trying to build SDK

Posted: Wed Oct 02, 2019 8:38 pm
by Geoff the Medio
If you're building on Windows, you don't need "clang-linux".

Take a step back and list what you've done and what the results were so far?

Re: Trying to build SDK

Posted: Wed Oct 02, 2019 11:08 pm
by em3
I'm pretty sure I followed the instructions, but I'll try again on an empty build directory.

Re: Trying to build SDK

Posted: Thu Oct 03, 2019 9:46 am
by em3
I did passed -G parameter just in case the toolkit is wrongly identified. I also passed -A x64, because otherwise cmake was

Code: Select all

PS C:\Users\miron> C:\dev\CMake\bin\cmake.exe -G "Visual Studio 15 2017" -S C:\Users\miron\Git\freeorion-sdk -B c:\users\miron\Documents\Build\freeorion-sdk  -A x64
-- The C compiler identification is MSVC 19.16.27025.1
-- The CXX compiler identification is MSVC 19.16.27025.1
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/miron/Documents/Build/freeorion-sdk

Code: Select all

PS C:\Users\miron> C:\dev\CMake\bin\cmake.exe --build C:\Users\miron\Documents\Build\freeorion-sdk --config RelWithDebInfo
Build failed. I forgot to save stderr to a file and console window can only fit so much. The report at the end notes:

Code: Select all

"C:\Users\miron\Documents\Build\freeorion-sdk\ALL_BUILD.vcxproj" (domyślny element docelowy) (1)->
"C:\Users\miron\Documents\Build\freeorion-sdk\boost.vcxproj" (domyślny element docelowy) (3)->
(element docelowy CustomBuild) ->
  C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(2
09,5): error MSB6006: Polecenie "cmd.exe" zakończone przez kod 1. [C:\Users\miron\Documents\Build\freeorion-sdk\boost.v
cxproj]

    Ostrzeżenia: 219
    Liczba błędów: 1
That is 219 warnings and one error. The error seems again to be about boost library. I'll run the build again (without cleaning) for a more concise report.

Re: Trying to build SDK

Posted: Thu Oct 03, 2019 9:49 am
by em3
One of the interesting warnings I did find was:

Code: Select all

CUSTOMBUILD : -- warning : Building the Windows version without DirectSound output [C:\Users\miron\Documents\Build\free
orion-sdk\openal-soft.vcxproj]
  --          This is probably NOT what you want!
I guess I'm missing Windows Platform SDK...

Edit: Yup, installing Windows 10 SDK fixed this warning.

Re: Trying to build SDK

Posted: Thu Oct 03, 2019 9:55 am
by em3
Again, the following error:

Code: Select all

CUSTOMBUILD : warning : toolset clang-linux initialization: can not find tool clang++ [C:\Users\miron\Documents\Build\f
reeorion-sdk\boost.vcxproj]
CUSTOMBUILD : warning : initialized from C:\Users\miron\Documents\Build\freeorion-sdk\boost-config.jam:20 [C:\Users\mir
on\Documents\Build\freeorion-sdk\boost.vcxproj]
  '"clang++"' is not recognized as an internal or external command,
  operable program or batch file.
  notice: will use 'clang++' for clang-linux, condition <toolset>clang-linux
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/tools\clang-linux.jam:63: in clan
  g-linux.init
  *** argument error
  * rule clang.init-cxxstd-flags ( toolset : condition * : version )
  * called with: ( clang-linux : <toolset>clang-linux :  )
  * missing argument version
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/tools\clang.jam:54:see definition
   of rule 'clang.init-cxxstd-flags' being called
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/build\toolset.jam:44: in toolset.
  using
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/tools\clang.jam:33: in clang.init
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/build\toolset.jam:44: in toolset.
  using
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/build\project.jam:1104: in using
  C:\Users\miron\Documents\Build\freeorion-sdk\boost-config.jam:20: in modules.load
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src\build-system.jam:255: in load-con
  fig
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src\build-system.jam:449: in load-con
  figuration-files
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src\build-system.jam:607: in load
  C:\Users\miron\Documents\Build\freeorion-sdk\boost-prefix\src\boost\tools\build\src/kernel\modules.jam:295: in import
  C:\Users\miron\Documents\Build\freeorion-sdk\boost-prefix\src\boost\tools\build\src/kernel/bootstrap.jam:139: in boos
  t-build
  C:\Users\miron\Documents\Build\freeorion-sdk\boost-prefix\src\boost\boost-build.jam:17: in module scope
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(209
,5): error MSB6006: Polecenie "cmd.exe" zakończone przez kod 1. [C:\Users\miron\Documents\Build\freeorion-sdk\boost.vcx
proj]
Kompilowanie projektu "C:\Users\miron\Documents\Build\freeorion-sdk\boost.vcxproj" wykonane (domyślne elementy docelowe
) - NIEPOWODZENIE.
NIEPOWODZENIE means FAILURE, FYI.

I'm not telling it to build anything with clang. It just somehow tries to when building boost.vcxproj.

Re: Trying to build SDK

Posted: Thu Oct 03, 2019 3:18 pm
by Geoff the Medio
em3 wrote: Thu Oct 03, 2019 9:46 amI also passed -A x64, because otherwise cmake was

Code: Select all

PS C:\Users\miron> C:\dev\CMake\bin\cmake.exe -G "Visual Studio 15 2017" -S C:\Users\miron\Git\freeorion-sdk -B c:\users\miron\Documents\Build\freeorion-sdk  -A x64
-- The C compiler identification is MSVC 19.16.27025.1
-- The CXX compiler identification is MSVC 19.16.27025.1
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/miron/Documents/Build/freeorion-sdk
Otherwise cmake was what? I would try without the -A x64 and from within the directory as the instructions say, not some other location... eg.

Code: Select all

C:\Users\Geoff\Desktop\sdkbtest>git clone https://github.com/freeorion/freeorion-sdk.git freeorion-sdk
C:\Users\Geoff\Desktop\sdkbtest>cd freeorion-sdk
C:\Users\Geoff\Desktop\sdkbtest\freeorion-sdk>mkdir build
C:\Users\Geoff\Desktop\sdkbtest\freeorion-sdk>cd build
C:\Users\Geoff\Desktop\sdkbtest\freeorion-sdk\build>cmake ..
C:\Users\Geoff\Desktop\sdkbtest\freeorion-sdk\build>cmake --build . --config RelWithDebInfo
Add -G "Visual Studio 15 2017" to cmake .. if it's otherwise picking the wrong compiler.

Re: Trying to build SDK

Posted: Thu Oct 03, 2019 8:13 pm
by em3
Geoff the Medio wrote: Thu Oct 03, 2019 3:18 pm
em3 wrote: Thu Oct 03, 2019 9:46 amI also passed -A x64, because otherwise cmake was
Otherwise cmake was what?
Sorry, I've got distracted while writing that. Otherwise CMake was choosing the x86 compiler instead of x64, and I wanted a x64 build.
I would try without the -A x64 and from within the directory as the instructions say, not some other location... eg.
I did try before and had the same errors. I just added it to make sure I'll have an x64 build.

I''m keeping sources and builds in separate hierarchy and I'll keep it that way. CMake itself seems to support this.
Add -G "Visual Studio 15 2017" to cmake .. if it's otherwise picking the wrong compiler.
I added the -G, as per instructions, during cmake generation step, not building. This parameter specifies, which generator to use.

Re: Trying to build SDK

Posted: Thu Oct 03, 2019 8:22 pm
by o01eg
em3 wrote: Thu Oct 03, 2019 8:13 pm
Geoff the Medio wrote: Thu Oct 03, 2019 3:18 pm
em3 wrote: Thu Oct 03, 2019 9:46 amI also passed -A x64, because otherwise cmake was
Otherwise cmake was what?
Sorry, I've got distracted while writing that. Otherwise CMake was choosing the x86 compiler instead of x64, and I wanted a x64 build.
I would try without the -A x64 and from within the directory as the instructions say, not some other location... eg.
I did try before and had the same errors. I just added it to make sure I'll have an x64 build.

I''m keeping sources and builds in separate hierarchy and I'll keep it that way. CMake itself seems to support this.
Add -G "Visual Studio 15 2017" to cmake .. if it's otherwise picking the wrong compiler.
I added the -G, as per instructions, during cmake generation step, not building. This parameter specifies, which generator to use.
To have x64 build you should use -G "Visual Studio 15 2017 Win64". Look at appveyor.yml file, it builds x64 SDK.

Re: Trying to build SDK

Posted: Thu Oct 03, 2019 8:42 pm
by em3
o01eg wrote: Thu Oct 03, 2019 8:22 pm To have x64 build you should use -G "Visual Studio 15 2017 Win64". Look at appveyor.yml file, it builds x64 SDK.
https://cmake.org/cmake/help/latest/gen ... -selection
The CMAKE_GENERATOR_PLATFORM variable may be set, perhaps via the cmake(1) -A option, to specify a target platform name (architecture). For example:

cmake -G "Visual Studio 15 2017" -A Win32
cmake -G "Visual Studio 15 2017" -A x64
cmake -G "Visual Studio 15 2017" -A ARM
cmake -G "Visual Studio 15 2017" -A ARM64

For compatibility with CMake versions prior to 3.1, one may specify a target platform name optionally at the end of the generator name. This is supported only for:

Visual Studio 15 2017 Win64
Specify target platform x64.
Visual Studio 15 2017 ARM
Specify target platform ARM.

Re: Trying to build SDK

Posted: Thu Oct 03, 2019 10:55 pm
by Geoff the Medio
I suggest trying the 32 bit build first. I suspect 64 isn't possible, due to vaguely recalling forum or github discussions about it, possibly relating to some of the dependencies. There's also not much point in a 64 bit build of FreeOrion... it doesn't need that much RAM per process.
Add -G "Visual Studio 15 2017" to cmake .. if it's otherwise picking the wrong compiler.
I added the -G, as per instructions, during cmake generation step, not building. This parameter specifies, which generator to use.
Sorry, I meant the other cmake call. The point is, don't add extra stuff unless needed and it doesn't work without it. Once it works, then try extra tweaks and options.

Re: Trying to build SDK

Posted: Thu Oct 03, 2019 11:39 pm
by em3
Geoff the Medio wrote: Thu Oct 03, 2019 10:55 pm I suggest trying the 32 bit build first. I suspect 64 isn't possible, due to vaguely recalling forum or github discussions about it, possibly relating to some of the dependencies. There's also not much point in a 64 bit build of FreeOrion... it doesn't need that much RAM per process.
My bad. I'm used to building everything 64 bit, so I tend to take it as default.
The point is, don't add extra stuff unless needed and it doesn't work without it. Once it works, then try extra tweaks and options.
Fair enough. I'll try to be more kosher about the build.

Re: Trying to build SDK

Posted: Fri Oct 04, 2019 9:48 am
by em3
I returned to building 32 bit. This time only 13 warnings, but still one error - building boost fails:

Code: Select all

  Performing configure step for 'boost'
  Building Boost.Build engine
  
  Generating Boost.Build configuration in project-config.jam for msvc...
  
  Bootstrapping is done. To build, run:
  
      .\b2
  
  To adjust configuration, edit 'project-config.jam'.
  Further information:
  
      - Command line help:
      .\b2 --help
       
      - Getting started guide: 
      http://boost.org/more/getting_started/windows.html
       
      - Boost.Build documentation:
      http://www.boost.org/build/
  
  Performing build step for 'boost'
  notice: found boost-build.jam at C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/boost-build.jam
  notice: loading Boost.Build from C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src
  notice: Searching 'C:\WINDOWS' 'C:\Users\miron' 'C:\Users\miron' 'C:\Users\miron\Documents\Build\freeorion-sdk\boost-prefix\src\boost\tools/build/src' 'C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/kernel' 'C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/util' 'C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/build' 'C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/tools' 'C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/contrib' 'C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/.' for site-config configuration file 'site-config.jam'.
  notice: Configuration file 'site-config.jam' not found in 'C:\WINDOWS' 'C:\Users\miron' 'C:\Users\miron' 'C:\Users\miron\Documents\Build\freeorion-sdk\boost-prefix\src\boost\tools/build/src' 'C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/kernel' 'C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/util' 'C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/build' 'C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/tools' 'C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/contrib' 'C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/.'.
  notice: Loading explicitly specified user configuration file:
      C:\Users\miron\Documents\Build\freeorion-sdk\boost-config.jam
  notice: Searching 'C:\Users\miron\Documents\Build\freeorion-sdk' for user-config configuration file 'boost-config.jam'.
  notice: Loading user-config configuration file 'boost-config.jam' from 'C:/Users/miron/Documents/Build/freeorion-sdk'.
  notice: [python-cfg] Configuring python...
  notice: [python-cfg]   user-specified version: "2.7"
  notice: [python-cfg]   user-specified cmd-or-prefix: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python2.7"
  notice: [python-cfg]   user-specified includes: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/include/python2.7"
  notice: [python-cfg]   user-specified libraries: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/lib"
  notice: [python-cfg] Checking interpreter command "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python2.7"...
  notice: [python-cfg] running command 'C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python2.7 -c "from sys import *; print('version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s' % (version_info[0],version_info[1],platform,prefix,exec_prefix,executable))" 2>&1'
  notice: [python-cfg] ...requested configuration matched!
  notice: [python-cfg] Details of this Python configuration:
  notice: [python-cfg]   interpreter command: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python2.7"
  notice: [python-cfg]   include path: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/include/python2.7"
  notice: [python-cfg]   library path: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/lib"
  notice: [python-cfg]   DLL search path: "<empty>"
  notice: [python-cfg] Checking for NumPy...
  notice: [python-cfg] running command 'C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python2.7 -c "import sys; sys.stderr = sys.stdout; import numpy; print(numpy.get_include())"'
  notice: [python-cfg] NumPy disabled. Reason:
  notice: [python-cfg]   C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python2.7 -c "import sys; sys.stderr = sys.stdout; import numpy; print(numpy.get_include())" aborted with 
  notice: [python-cfg]   Traceback (most recent call last):
    File "<string>", line 1, in <module>
  ImportError: No module named numpy
  notice: [python-cfg] Configuring python...
  notice: [python-cfg]   user-specified version: "3.5"
  notice: [python-cfg]   user-specified cmd-or-prefix: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python3.5"
  notice: [python-cfg]   user-specified includes: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/include/python3.5"
  notice: [python-cfg]   user-specified libraries: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/lib"
  notice: [python-cfg] Checking interpreter command "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python3.5"...
  notice: [python-cfg] running command 'C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python3.5 -c "from sys import *; print('version=%d.%d\nplatform=%s\nprefix=%s\nexec_prefix=%s\nexecutable=%s' % (version_info[0],version_info[1],platform,prefix,exec_prefix,executable))" 2>&1'
  notice: [python-cfg] ...requested configuration matched!
  notice: [python-cfg] Details of this Python configuration:
  notice: [python-cfg]   interpreter command: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python3.5"
  notice: [python-cfg]   include path: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/include/python3.5"
  notice: [python-cfg]   library path: "C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/lib"
  notice: [python-cfg]   DLL search path: "<empty>"
  notice: [python-cfg] Checking for NumPy...
  notice: [python-cfg] running command 'C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python3.5 -c "import sys; sys.stderr = sys.stdout; import numpy; print(numpy.get_include())"'
  notice: [python-cfg] NumPy disabled. Reason:
  notice: [python-cfg]   C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python3.5 -c "import sys; sys.stderr = sys.stdout; import numpy; print(numpy.get_include())" aborted with 
  notice: [python-cfg]   Traceback (most recent call last):
    File "<string>", line 1, in <module>
  ImportError: No module named 'numpy'
CUSTOMBUILD : warning : toolset clang-linux initialization: can not find tool clang++ [C:\Users\miron\Documents\Build\freeorion-sdk\boost.vcxproj]
CUSTOMBUILD : warning : initialized from C:\Users\miron\Documents\Build\freeorion-sdk\boost-config.jam:20 [C:\Users\miron\Documents\Build\freeorion-sdk\boost.vcxproj]
  '"clang++"' is not recognized as an internal or external command,
  operable program or batch file.
  notice: will use 'clang++' for clang-linux, condition <toolset>clang-linux
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/tools\clang-linux.jam:63: in clang-linux.init
  *** argument error
  * rule clang.init-cxxstd-flags ( toolset : condition * : version )
  * called with: ( clang-linux : <toolset>clang-linux :  )
  * missing argument version
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/tools\clang.jam:54:see definition of rule 'clang.init-cxxstd-flags' being called
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/build\toolset.jam:44: in toolset.using
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/tools\clang.jam:33: in clang.init
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/build\toolset.jam:44: in toolset.using
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src/build\project.jam:1104: in using
  C:\Users\miron\Documents\Build\freeorion-sdk\boost-config.jam:20: in modules.load
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src\build-system.jam:255: in load-config
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src\build-system.jam:449: in load-configuration-files
  C:/Users/miron/Documents/Build/freeorion-sdk/boost-prefix/src/boost/tools/build/src\build-system.jam:607: in load
  C:\Users\miron\Documents\Build\freeorion-sdk\boost-prefix\src\boost\tools\build\src/kernel\modules.jam:295: in import
  C:\Users\miron\Documents\Build\freeorion-sdk\boost-prefix\src\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build
  C:\Users\miron\Documents\Build\freeorion-sdk\boost-prefix\src\boost\boost-build.jam:17: in module scope
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets(209,5): error MSB6006: Polecenie "cmd.exe" zakończone przez kod 1. [C:\Users\miron\Documents\Build\freeorion-sdk\boost.vcxproj]
Kompilowanie projektu "C:\Users\miron\Documents\Build\freeorion-sdk\boost.vcxproj" wykonane (domyślne elementy docelowe) - NIEPOWODZENIE.
Note, that even though:

Code: Select all

  Generating Boost.Build configuration in project-config.jam for msvc...
... it still tries to use clang in a custom build step.

I'll investigate the boost.vcproj file.

Re: Trying to build SDK

Posted: Fri Oct 04, 2019 9:51 am
by em3
My boost-config.jam, as generated by CMake:

Code: Select all

using python
    : 2.7  # version
    : C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python2.7  # cmd-or-prefix
    : C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/include/python2.7 # includes
    : C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/lib # libraries
    ;

using python
    : 3.5  # version
    : C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/bin/python3.5  # cmd-or-prefix
    : C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/include/python3.5 # includes
    : C:/Users/miron/Documents/Build/freeorion-sdk/INSTALL/lib # libraries
    ;

# detect the location of the Mac OSX SDK.
using clang
    : # version (not used)
    : # cmd (compiler; not used)
    : <root>
    ;
To contrast, project-config.jam:

Code: Select all

# Boost.Build Configuration 
# Automatically generated by bootstrap.bat 
 
import option ; 
 
using msvc ; 
 
option.set keep-going : false ; 

Re: Trying to build SDK

Posted: Fri Oct 04, 2019 12:03 pm
by Geoff the Medio
Are you running this from the Visual Studio 2017 Developer Command Prompt? Perhaps the Boost stuff is looking for environment variables that are missing if using another command prompt or configuration thereof?