Skip to content

msvc: Use different output directories depending on build type #1615

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

Closed
wants to merge 1 commit into from

Conversation

stinos
Copy link
Contributor

@stinos stinos commented Nov 12, 2015

This allows multiple versions (e.g. Debug/Release, x86/x64) of micropython.exe
to co-exist instead and also solves potential problems where msbuild does not
completely rebuild the output and/or pdb files when switching between builds,
which in turn can cause linker errors in dependent projects.

By default exe/map/... files go in windows/build/$(Configuration)$(Platform)

After each build micropython.exe is still copied from the above directory to
the windows directory though, as that is consistent with the other ports and
the test runner by default uses that location as well.

Also rename env.props -> path.props which is a clearer name,
and add ample documentation in the affected build files.

(also see discussion in #1538)

This defaults to, for example for Configuration = Debug and Platform = x64:

micropython [PyBaseDir]
├── ...
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it ok to have non-ASCII characters in this file? I know it's just a comment, and the xml encoding is specified as utf-8, but ...?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question but I'm not aware of any problems. msbuild is quite picky about what you put in the files and it loads this one so it should be ok. I actually just copy-pasted the output from the tree command but if you want I can replace it with pure ascii characters

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you don't mind, I'd rather pure ASCII, just in case one day someone wants to view the file in a simple text editor that doesn't support utf-8.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed (I'll do another PR for the failing windows build due to unrelated changes)

@stinos stinos force-pushed the windows-builddir branch 2 times, most recently from c3515d5 to 86f1dde Compare November 16, 2015 08:50
This allows multiple versions (e.g. Debug/Release, x86/x64) of micropython.exe
to co-exist instead and also solves potential problems where msbuild does not
completely rebuild the output and/or pdb files when switching between builds,
which in turn can cause linker errors in dependent projects.

By default exe/map/... files go in windows/build/$(Configuration)$(Platform)

After each build micropython.exe is still copied from the above directory to
the windows directory though, as that is consistent with the other ports and
the test runner by default uses that location as well.

Also rename env.props -> path.props which is a clearer name,
and add ample documentation in the affected build files.

(also see discussion in micropython#1538)
@pfalcon
Copy link
Contributor

pfalcon commented Dec 11, 2015

Sorry, this patch somehow slipped from attention.

@pfalcon pfalcon closed this Dec 11, 2015
@pfalcon
Copy link
Contributor

pfalcon commented Dec 11, 2015

(Merged now)

@stinos
Copy link
Contributor Author

stinos commented Dec 12, 2015

Thanks!

@stinos stinos deleted the windows-builddir branch December 21, 2015 20:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants