Torque, cmake, compiler, OS

[Bloodknight]

Been some issues and discussion lately regards different compilers, different platforms and even different versions of cmake, figured we could narrow down issues to specific versions that don't work with each other for whatever reason. This could then be looked at in terms of making it just work across all variants where possible.

So this is sort of a questionnaire, ideally if we can get the following information

• Torque version, either tagged versions from the master branch (3.8 3.9 3.10 etc) or devhead rough month of download would be nice but possibly not important.
• OS (win8, win10 ubuntu 16.04, 18.04 etc + bitness 32/64
  
• cmake version
  
• compiler version VS2015 VS1017 GCC4
  
• any notes, pass/fail anything special you did to fix it, hack it, whatever you did to get it working if it was iffy
  

[Bloodknight]

Devhead, January

Win10 pro 64

cmake 3.13.4

VS2017

worked fine from clean install

Edited February 24, 2019 by Bloodknight

[JeffR]

Devhead, Feb.

Win10 Home 64

cmake 3.11.2 and 3.12.4

VS2017

Worked on both machines from clean install.

[suncaller]

Version: Devhead, Feb.

OS: Windows 10 Pro 64

CMake: 3.12.1, 3.13.4

Generator: Visual Studio 15 2017, Ninja

Compiler: Visual Studio 2017, Clang 7

Visual Studio 2017: Works seamlessly from clean install. No hacks required.

Clang 7: Fails, currently unable to resolve issues.

[Steve_Yorkshire]

Development Feb 2nd

Win10 Home 64

Cmake 3.13.4 64

VS2017 64

All quiet on the Western Front.

I noticed everything (i.e. shaders) load faster if you put the shaders/procedural folder back in with the autogen so they don't have to keep building everytime you load a new level/mission file.