Closed ridilculous closed 1 year ago
How --build-dir=
works right now is kind of funky and probably not matching your expectations. It sets up the entire build relative to some directory x
, but expects make
to be invoked still from the root directory. Here is it operating on Linux
$ ./configure.py --build-dir=/tmp/x
...
$ make -f /tmp/x/Makefile
...
I think (besides path differences) this should also work on Windows with nmake
.
Ahh. Thanks a lot for pointing this out! I didn't notice that the release build put the Makefile
in the root.
This works perfectly:
call "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvars64.bat
python configure.py --cc=msvc --os=windows --debug-mode --with-build-dir=build/debug --program-suffix=D.exe --library-suffix=D
nmake /F build/debug/Makefile
nmake /F build/debug/Makefile check
On another note, even though it makes completely sense, it wasn't clear to me from the docs that when set, --program-suffix
needs an explicit .exe
suffix.
I'm not sure if this is a bug or if i'm using it wrong but whatever i try it seems like
--with-build-dir
is ignored by the followingnmake
.Here's how i'm testing (using the release-3 branch):
I also tried
.\build_debug
and an absolute path butnmake
always tries to build in thebuild
dir. It works when i don't use--with-build-dir
.This is the output i get: