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.
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
MSVS test fixes and minor changes to msvs tool #4610
Changes from all commits
9e7f85a
518b512
357ce53
76839d9
dc9673c
d536184
07feba3
f3fdec1
705f579
da65616
c815981
f13babb
ca866a2
5584941
8e627eb
5b77239
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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).