Skip to content
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

Building for VS2012 and VS2013 #81

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

justinstenning
Copy link
Contributor

Just to make it easier, here are the build scripts for VS2012 and VS2013

Conflicts:
	BuildVS2012/build.proj
	BuildVS2012/libudis86.vcxproj
	BuildVS2012/libudis86.vcxproj.filters
	BuildVS2012/udcli.vcxproj.filters
	BuildVS2013/build.proj
	BuildVS2013/libudis86.vcxproj
	BuildVS2013/libudis86.vcxproj.filters
	BuildVS2013/udcli.vcxproj.filters
@assarbad
Copy link

assarbad commented Feb 4, 2014

I have a little script over on Bitbucket which will make your NT script a little more concise. And as a side-effect it lets you simply choose the VS version you want, and whether you want the amd64 toolchain or so and then does the right thing by looking up the correct paths to the VS versions in the registry:

Feel free to use. It's in the public domain (CC0) and if that isn't enough, I can make it available under another permissive license like MIT/BSD/zlib license.

@justinstenning
Copy link
Contributor Author

Looks like a good option for replacing the buildVS20xx.bat file with a single one. I think we still need the duplicate solution and project files however.

Thanks for pointing the script out, I may try to use that for some of my other projects.

@assarbad
Copy link

assarbad commented Feb 5, 2014

I've had good experiences with premake4. It certainly is limited and you may hit those limits in complex scenarios, but this project looks simple enough. I'll see whether I can write up a quick one. And yes, you'll still have to have the project to build, but IIRC VS2008 could use VS2005 projects and solutions and VS2012 and 2013 could use those from 2010. Basically everything starting with VS2010 is MSBuild based (which is another option that would work across VS versions, using a single project).

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.

2 participants