-
-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MSVS test fixes and minor changes to msvs tool #4610
Merged
Merged
Changes from 4 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
9e7f85a
Fix MSVS tests and minor changes to Tool/msvs.py.
jcbrill 518b512
Merge branch 'Master' into jbrill-msvs-tests
jcbrill 357ce53
Add safe HOST_ARCH to sconstruct/sconscript environment for MSVS test…
jcbrill 76839d9
Update Tool/msvs.py, update MSVS tests; and add additional tests for …
jcbrill dc9673c
Update MSVS new test file headers based on the template test file hea…
jcbrill d536184
Remove MSVSProject argument projectguid and replace with MSVS_PROJECT…
jcbrill 07feba3
Minor code order refactor in msvs.py.
jcbrill f3fdec1
Remove win32 platform specification (i.e., platform = 'win32') from M…
jcbrill 705f579
Bug fix in msvs.py: the value for the construction value 'nokeep' was…
jcbrill da65616
Fix: normalize case for solution file extension and file name for str…
jcbrill c815981
Merge branch 'master' into jbrill-msvs-tests
jcbrill f13babb
Update CHANGES.txt and RELEASE.txt [ci skip]
jcbrill ca866a2
Merge branch 'master' into jbrill-msvs-tests
jcbrill 5584941
Add optional keyword argument auto_filter_projects to MSVSSolution.
jcbrill 8e627eb
Merge branch 'master' into jbrill-msvs-tests
jcbrill 5b77239
Update RELEASE.txt entries to be consistent with current formatting.
jcbrill File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should ever be writing into the src directory of a variant (or into a Repository())
What's the reason for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some previous discussion here: #4612 (comment) and a number of successive posts.
The generated solution and project files have source code references which is why I'm guessing they were originally written the way the are. Opening the visual studio solution in the source directory will still build in the variant directory.
If the project artifacts were generated in the variant build directory, then all source files would need relative paths back to the source directory. There are a number of user specified locations that may be affected as well.
The project files have been written this way going way back (possibly to version 1). While the project file were written with a placeholder in the variant dir, the solution file was generated in the variant dir rather than source folder.
Getting the relative links to the source file locations is not easy. I was working on attempting the generate the solution/project files in their own folder (i.e., not the source folder and not the variant dir) but didn't know how some of the user specified paths/files should work. For example, is a file specified with no path because the generated environment locates it?
As one would have one project file may use multiple variant directories (i.e., one build folder for debug and one build folder for release). There is only one solution file and one project file (with both msvs variants). If there were two build folders the solution and project files would have to written to multiple folders (i.e., multiple copies).