search

ericwa / ericw-tools

Quake/Hexen 2 Map compiling tools - branch of http://disenchant.net/utils
http://ericwa.github.io/ericw-tools
GNU General Public License v2.0
309 stars 56 forks source link

Compilation on Windows is too complicated. #429

Open FriendlyCat666 opened 2 weeks ago

FriendlyCat666 commented 2 weeks ago

Hi,

I successfully managed to compile the brushbsp branch on Linux, but I couldn't do the same on Windows.

The script ./build-windows.ps1 uses commands that are quite uncommon for the average Windows user. Some of these commands, like choco, are not even mentioned in the requirements, and others, like py, seem to be missing on my PC(64 bit) (I assume this should be a Python program). I am not a master of C/C++ and know absolutely nothing about cmake.

Can anyone share their setup for compiling this branch on Windows?

Thank you.

Paril commented 2 weeks ago

I'm pretty sure that the ps1 script is for our CI, not necessarily for end users. You should be able to just open the project in Visual Studio via its built-in cmake support. You'll have to use vcpkg or similar to install the dependencies, but it should 'just work'; it's been a while since I tried building it from a clean environment though.

dsvensson commented 1 week ago

fyi, if you install embree via vcpkg you'll might risk getting degraded performance just like when using the distribution build of embree on Linux. Use the Intel installer for embree instead, or the binaries from embree release page as then you get the one compiled with ISPC. Building embree under the intended conditions on your own is pretty messy unless you already have the oneapi toolchain setup. See #352.

I wonder if embree exposes some nice runtime-function to detect what type of build it is. Would be valuable for light to print as it was a massive performance difference back then. But it was a while ago since I spotted that inconsistency so perhaps better to reevaluate if it's still the case.