Ah, so that's just the error that `python setup.py build` would have returned,
it's not specific to conda-build.
As for what version you need, that's where things get fun:
- Python 2.7 = Visual Studio 2008
- Python 3.0->3.4 = Visual Studio 2010
- Python 3.5+ = Visual Studio 2015
For 2.7, Microsoft released this handy little bundle (thanks Steve Dower!):
https://www.microsoft.com/en-us/download/details.aspx?id=44266
I've been lucky enough to always have MSDN subscriptions and full VS
installations so I'm not sure how your mileage will fair with the
community/free editions. You could sign up for an AppVeyor or Anaconda account
if procuring VS proves problematic.
Trent.
-----Original Message-----
From: Bill Janssen [mailto:[email protected]]
Sent: Friday, December 18, 2015 8:02 PM
To: Trent Nelson <[email protected]>
Cc: [email protected]; [email protected]
Subject: Re: [python-win32] building a complicated Python application on Windows
Hmmm, I'm getting an error message from 'conda build':
Warning: Couldn't find Visual Studio: 'C:\\Program Files (x86)\\Common
Files\\Microsoft\\Vi...'
So I guess installing conda-build doesn't do everything it needs to?
How would I know which version of Visual Studio to install, and where to find
it?
Bill
Trent Nelson <[email protected]> wrote:
> Conda is well suited to this. I use it to bundle all sorts of stuff on
> Windows. (You write recipes (see https://github.com/conda/conda-recipes for
> examples), then 'conda build' them, which produces a package that can be
> subsequently installed with conda install. Can sign up to anaconda.org and
> then upload the package into your own channel, such that a plain 'conda
> install -c janssen foobar' will install your package and all the deps (which
> were specified in the recipe/meta.yaml).
>
> Sent from my iPhone
>
> > On Dec 16, 2015, at 13:00, Bill Janssen <[email protected]> wrote:
> >
> > I'd like to build a Python-based deliverable for Windows. It
> > includes many gnarly packages, like numpy, scipy, statsmodel,
> > ggplot, kivy, ZODB, ZEO, etc. They include Cython modules (and
> > scipy may even require Fortran, for all I know).
> >
> > On OS X, I build this all from source by starting with Kivy, which
> > is packaged as a venv inside an OS X application, and add in the
> > other stuff. But I'm not sure this is the best way to proceed on
> > Windows (7, 8, and 10). I'm also used to using mingw on Windows,
> > but again, I'm not sure that's appropriate.
> >
> > Any advice would be appreciated...
> >
> > Bill
> > _______________________________________________
> > python-win32 mailing list
> > [email protected]
> > https://mail.python.org/mailman/listinfo/python-win32
_______________________________________________
python-win32 mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-win32
