This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
There is two different build configuration (Debug/Release) and two different debug platforms (x64/Win32)
When I build a static library project, it generates .lib file based on build configuration and build platform:
build\
release\x64\mylib.lib
debug\x64\mylib.lib
Is this a normal behavior with Visual Studio? As far as I know, we can combine Release and Debug configuration into a single .lib file.
How can I do that in VS2022?
If that is not possible, I just separate lib folder for different build configuration (in my other project that uses mylib):
lib\
release\x64\
debug\x64\
Is this a normal behavior with Visual Studio?
Yes.
As far as I know, we can combine Release and Debug configuration into a single .lib file.
This is incorrect.
Alright, maybe I just seen it in a dream. But I barely remember there is single .lib that can be used for both Debug and Release, somewhere in a c++ library.
Thank you for the answer, @RLWA32
FYI - combining debug and release versions. Ultimately, the duplication of symbols and module names would be problematic.
Single source file for static lib -
Combining source and debug versions into a single static lib -
@thebluetropics And if you tried to insert two .obj files with the same name (not distinguished by paths) into a single static library only one would be included.
which one will be included?
What is that lib command? And where is the command located at?
From managing-a-library
"When an object that has the same name exists in more than one input file, LIB puts the last object specified in the LIB command into the output library."