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

Support for Microsoft Visual C++ Compiler for Python 2.7 #218

Closed
petrushy opened this issue Sep 29, 2014 · 7 comments
Closed

Support for Microsoft Visual C++ Compiler for Python 2.7 #218

petrushy opened this issue Sep 29, 2014 · 7 comments
Labels
locked [bot] locked due to inactivity

Comments

@petrushy
Copy link

Microsoft has a package of compilers for python for windows:
http://www.microsoft.com/en-us/download/details.aspx?id=44266

The installer seems to install by default to current user\AppData\Local\Programs\Common\Microsoft\Visual C++ for Python\9.0\vcvarsall.bat

if installed by command line for all users it installs to:
C:\Program Files (x86)\Common Files\Microsoft\Visual C++ for Python\9.0\vcvarsall.bat

conda-build/windows.py assumes it's located under a specific place at C:\Program Files(x86)\Micros... (line 67-69).
Are there some setting to override this, otherwise I would propose to have such?

@asmeurer
Copy link
Contributor

I don't know if a way of overriding is necessary. We just need to update the code to look in the other location in addition to the current one.

@tpn
Copy link
Contributor

tpn commented Sep 29, 2014

What would be even more awesome is wrapping the entire thing as a conda package, then we could simply specify it as a dep in recipes (or maybe implicitly have it as a dep if platform is windows && python == 2.7).

@asmeurer
Copy link
Contributor

Can it be installed in a relocatable way?

@tpn
Copy link
Contributor

tpn commented Sep 29, 2014

No idea.

@petrushy
Copy link
Author

petrushy commented Oct 6, 2014

I have tried with the msiexec command and setting variables such as INSTALLDIR and TARGETDIR but it seems not to respond to that.

@msarahan
Copy link
Contributor

msarahan commented May 9, 2016

Closed by #861

@msarahan msarahan closed this as completed May 9, 2016
@github-actions
Copy link

Hi there, thank you for your contribution!

This issue has been automatically locked because it has not had recent activity after being closed.

Please open a new issue if needed.

Thanks!

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Apr 23, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity
Projects
None yet
Development

No branches or pull requests

4 participants