Re: [Py2exe-users] Building a .exe under Windows 10

[Fahlgren, E. <eri...@sm...>]

Hi Werner,

We have all sorts of stuff from Cython, scipy, numpy, wxPython and so on, but the best bet is our home-built VTK which builds with the (Py2.7-incorrect) MSVC 2010 compiler, so I'm guessing that the unsanctioned compiler is linking VTK internals to all those system libs.

We make sure to run the vcredist_x64.exe for that compiler during product installation, and that seems to get everything we need.

Eric

> -----Original Message-----
> From: Werner [mailto:wer...@gm...]
> Sent: Tuesday, October 06, 2015 13:08
> To: py2...@li...
> Subject: Re: [Py2exe-users] Building a .exe under Windows 10
> 
> On 10/6/2015 16:51, Fahlgren, Eric wrote:
> > David,
> >
> > In my 2.7.10 builds using py2exe 0.6.9 on Win 7, I see those plus more
> > being collected into the build directory, but then my next step in
> > packaging deletes them.  They are Windows version-specific files that
> > you can and should leave out of your product packaging.  (Now all you
> > need to do is figure out how to suppress any messages about them.)
> >
> > For completeness, I've included the list of files I drop from our installer.
> I don't get any of these into my build directory, with py2exe 0.6.9 on Win 8.1
> and py 2.7.
> 
> What uses these DLL's?  Do you use that in your application?
> 
> IIRC, Windows version specific stuff should not be included, but then you have
> to ensure that it the correct versions are on the deployment maschine.
> 
> To exclude you could use "dll_excludes".
> 
> Werner
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Py2exe-users mailing list
> Py2...@li...
> https://lists.sourceforge.net/lists/listinfo/py2exe-users