More flexibility to build Debug components#136
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The goal of this PR is to:
/MTbut GoogleTest with/MD(due togtest_force_shared_crtinmob). Trying to build the test configuration of USVFS with/MDinstead of/MTthen throws issue with some missing boost components, especially for x86. The fix for this is to move theReleaseTestconfiguration of USVFS to/MD(theReleaseconfiguration will be untouched) and to add the missing boost components.GTEST_ROOT.mob(instead of RelWithDebInfo).The following components support debug mode:
libbsarch- Sincelibbsarchis not built bymob, this only changes the archive that is downloaded.python- This build Python in debug mode. Some changes have been made toplugin_pythonto match the changes.pyqt- This build PyQt in debug mode, but requires Python in debug mode.PyQt debug build is a mess, so there are many "workaround", but I made sure to not modify the release path.