Closed SirLynix closed 3 years ago
I have fixed it on dev branch.
Seems good. Thank you!
I still have the bug, even with the latest xmake version, following a xmake update -s
, and an updated VS2019.
D:\GitHub\chip8-emulator>xmake --version
xmake v2.3.9+202011250023, A cross-platform build utility based on Lua
Copyright (C) 2015-present Ruki Wang, tboox.org, xmake.io
_
__ ___ __ __ __ _| | ______
\ \/ / | \/ |/ _ | |/ / __ \
> < | \__/ | /_| | < ___/
/_/\_\_|_| |_|\__ \|_|\_\____|
by ruki, xmake.io
�� Manual: https://xmake.io/#/getting_started
�� Donate: https://xmake.io/#/sponsor
You can download latest package and try it again from ci. https://github.com/xmake-io/xmake/suites/1692663518/artifacts/31789098
Describe the bug
Okay it's a bit weird.
I have a project in
C:\Projets\Burgwar\BurgWar
on my computer, and I noticed that sometimes aC:\Projets\Burgwar\BurgW
appeared, with a .xmake folder in it.I investigated and it seems to occur when using vsxmake generator.
Expected behavior
That xmake uses the right full path.
Related Environment
Please provide compiling and running environment information:
Additional context
To reproduce (on Windows):
Opens the visual studio solution and use it to build.
In my case a
C:\Projets\Tests\xmake-build\test_pat
folder appeared.I added a
in xmake/core/project/project.lua which shows this in Visual Studio to confirm:
Notice the missing h.
Edit: it seems to come from the
XMAKE_CONFIGDIR
env, when enabling diagnosis informations in vsxmake I get this: