github XiONDiGiTaL/EmblemWeave v0.1.23
EmblemWeave 0.1.23

latest releases: v0.1.41, v0.1.40, v0.1.39...
6 days ago

EmblemWeave 0.1.23

A build folder left behind by an older release no longer breaks the build with clang++'s "unknown argument"

Install

  1. Download EmblemWeave-v0.1.23-windows-x64.zip below and unzip it into a folder of its own.
  2. Run EmblemWeave.exe.
  3. On Game Setup, choose your dump. On Overview, press Build the game (once), then Play.

sha256 of the zip: 6ef5e7ca8479ae1beee868e711a721ca72e7f0c56ef6894ea45b64d41ab95bee

The error in #25

clang++: error: unknown argument: '-clang:-fmacro-prefix-map=…'
clang++: error: no such file or directory: '/W3'

Both lines are the same mistake: flags written for clang-cl reaching the clang++ driver. Two things made that possible.

The engine's own check for which driver is compiling was CMAKE_CXX_SIMULATE_ID STREQUAL "MSVC", which decides how the
-fmacro-prefix-map argument is spelled. On a Windows host that value is MSVC for the clang++ driver as well as for clang-cl,
so the check was true in both cases and the -clang: form went to clang++, which has no such argument. It goes by
CMAKE_CXX_COMPILER_FRONTEND_VARIANT now, which is only MSVC for clang-cl.

The other half is the build folder itself. A folder configured by an older release was configured for clang++, and CMake keeps the
flags it wrote for the first compiler when one is swapped in afterwards. The build script now reads the compiler a folder was
configured with before it configures anything, and starts the folder over when that is not the compiler it is about to use, so no
stale MSVC /W3 reaches a GNU driver.

Verified

  • A fresh clang++ configure of the engine project now configures and compiles fefw_main.cpp with no argument error (-fmacro-prefix-map
    as it is, no -clang:).
  • A build folder configured for clang++ and then built with the script prints that it is starting the folder over and builds
    fefw_main.cpp with clang-cl (exit 0), which is the state the report was in.
  • The clang-cl release folder still configures and compiles that target after the change (exit 0).
  • Not checked: a full engine build from scratch on a machine other than this one, and the reporter's own machine. Their folder is
    fixed by the script the first time they press Build the game on 0.1.23.

Don't miss a new EmblemWeave release

NewReleases is sending notifications on new releases.