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

MS Visual Studio Auto configuration #165

Closed
pauldaustin opened this issue May 1, 2015 · 3 comments
Closed

MS Visual Studio Auto configuration #165

pauldaustin opened this issue May 1, 2015 · 3 comments

Comments

@pauldaustin
Copy link
Contributor

I'm working on a patch that will simplify the setup of MSVC projects.

The patch adds the following configuration section.

<msvc>
  <version>10.0</version>
  <windowsSdkVersion>7.1A</windowsSdkVersion>
</msvc>

The configuration allows defining the MS Visual Studio version number.
This will then auto detect the Visual Studio Home. If the version is not
specified it will look for the VSxxxCOMNTOOLS environment variables to
see which
versions exist and use the maximum available version.

The configuration also allows selecting the windowsSdkVersion. If not
specified it will look in the C:\Program Files (x86)\Microsoft
SDKs\Windows or C:\Program Files (x86)\Windows Kits for available
versions.

The linker and compilers will then be configured with default includes
and library paths from both the visual studio and windows sdk homes.

I'm almost ready to create a pull request for this feature. I just need to verify the amd64 compilation and linking.

@ctrueden
Copy link
Contributor

ctrueden commented May 1, 2015

Sounds great, @pauldaustin. Thanks for the update!

@ctrueden ctrueden added this to the unscheduled milestone Aug 6, 2015
@eyalg1972
Copy link

Was it created? If so- how can I use it?

@ctrueden
Copy link
Contributor

ctrueden commented May 9, 2017

@eyalg1972 It might have been one (or more) of: #166, #168, #170, #173, #174.

Regardless, I'm closing this issue, since it's very old, and probably addressed, and even if not, it's not moving forward anymore, nor could anyone else feasibly pick it up to work on it.

@ctrueden ctrueden closed this as completed May 9, 2017
@ctrueden ctrueden removed this from the unscheduled milestone May 9, 2017
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

No branches or pull requests

3 participants