If you build ViGEmClient on its own (through Visual Studio), you'll end up with a directory structure like this, where output files are written to top-level directories called bin (for DLLs) or lib (for static libs), e.g.:
ViGEmClient/ViGEmClient.sln
ViGEmClient/src/ViGEmClient.vcxproj
ViGEmClient/lib/release/x64/ViGEmClient.lib
I cloned ViGEmClient into my own project as a submodule, giving me a directory structure like this:
To simplify the build process within Visual Studio, I added the project (ViGEmClient.vcxproj) to my solution (myproject.sln). However, I noticed that when I build ViGEmClient to generate static libs, they end up in an unexpected location:
myproject/build/myproject.sln
myproject/build/myproject.vcxproj
myproject/build/lib/release/x64/ViGEmClient.lib <-- currently, output libs are written here
myproject/external/ViGEmClient/lib/release/x64/ViGEmClient.lib <-- but they should really be here
This is simply because the output directories configured in ViGEmClient.vcxproj are defined relative to $(SolutionDir). This change updates those paths to be resolved relative to $(ProjectDir), so that output files always end up in the expected locations (ViGEmClient/lib or ViGEmClient/bin) regardless of whether the library is built on its own or within another solution.
nefarius
commented
2 years ago
If you build ViGEmClient on its own (through Visual Studio), you'll end up with a directory structure like this, where output files are written to top-level directories called
bin(for DLLs) orlib(for static libs), e.g.:ViGEmClient/ViGEmClient.slnViGEmClient/src/ViGEmClient.vcxprojViGEmClient/lib/release/x64/ViGEmClient.libI cloned ViGEmClient into my own project as a submodule, giving me a directory structure like this:
myproject/build/myproject.slnmyproject/build/myproject.vcxprojmyproject/external/ViGEmClient/ViGEmClient.slnmyproject/external/ViGEmClient/src/ViGEmClient.vcxprojTo simplify the build process within Visual Studio, I added the project (
ViGEmClient.vcxproj) to my solution (myproject.sln). However, I noticed that when I build ViGEmClient to generate static libs, they end up in an unexpected location:myproject/build/myproject.slnmyproject/build/myproject.vcxprojmyproject/build/lib/release/x64/ViGEmClient.lib<-- currently, output libs are written heremyproject/external/ViGEmClient/ViGEmClient.slnmyproject/external/ViGEmClient/src/ViGEmClient.vcxprojmyproject/external/ViGEmClient/lib/release/x64/ViGEmClient.lib<-- but they should really be hereThis is simply because the output directories configured in
ViGEmClient.vcxprojare defined relative to$(SolutionDir). This change updates those paths to be resolved relative to$(ProjectDir), so that output files always end up in the expected locations (ViGEmClient/liborViGEmClient/bin) regardless of whether the library is built on its own or within another solution.Thanks!