Are the header files and .lib files for the MSW binaries of wxPython
available? Actually I'm mostly interested in the wxMSW headers and .lib
as I've got a python module that accesses wxWindows directly.
My solution so far is that I compile wxWindows myself just to get those
files but since you're producing windows binaries, it would be good to
put the header and .lib files and anything else that might be needed for
python C-modules that have to access wxWindows directly into the
installer as well. A separate installer or just a zip file would be fine
too.
Are the header files and .lib files for the MSW binaries of wxPython
available?
Not currently.
but since you're producing windows binaries, it would be good to
put the header and .lib files and anything else that might be needed for
python C-modules that have to access wxWindows directly into the
installer as well. A separate installer or just a zip file would be fine
too.
I've done it a couple times in the past. I'll look into doing it again and
automating it. Are just FINAL builds enough or do you need debug or hybrid
builds too? IIRC, the last time I did it and included a debug build the
.zip file was HUGE (something like 30-40 MB) because of the debug info that
is included. It's probably gone up since then. Is something that big still
worth the upload/download time?
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
> but since you're producing windows binaries, it would be good to
> put the header and .lib files and anything else that might be needed for
> python C-modules that have to access wxWindows directly into the
> installer as well. A separate installer or just a zip file would be fine
> too.
I've done it a couple times in the past. I'll look into doing it again and
automating it. Are just FINAL builds enough or do you need debug or hybrid
builds too?
I'd say, final and hybrid would be good. We're currently using the
hybrid version of the binaries.
IIRC, the last time I did it and included a debug build the
.zip file was HUGE (something like 30-40 MB) because of the debug info that
is included. It's probably gone up since then. Is something that big still
worth the upload/download time?
We can build a Debug version ourselves if necessary, so as far as I'm
concerned you don't have to bother with those. The .lib file for the
hybrid dll is less than 4MB so size shouldn't be a problem there.
One other thing: I build the python module with distutils. On Unix I can
execute the wx-config script to get the compiler flags for wxWindows.
For the window's build I've more or less hardcoded them in the setup.py
(copied from wxPython's setup.py ). Would it be possible to write the
compiler settings used into some wxPython module so that I could use
something like this in my setup.py to figure out the settings:
Include and library directories probably can't be handled easily in this
way, but they're more static and easier to figure from the prefix which
on windows will probably have to be provided by the person building the
extensions anyway.
> Are the header files and .lib files for the MSW binaries of wxPython
> available?
Not currently.
> but since you're producing windows binaries, it would be good to
> put the header and .lib files and anything else that might be needed for
> python C-modules that have to access wxWindows directly into the
> installer as well. A separate installer or just a zip file would be fine
> too.
I've done it a couple times in the past. I'll look into doing it again and
automating it. Are just FINAL builds enough or do you need debug or hybrid
builds too? IIRC, the last time I did it and included a debug build the
.zip file was HUGE (something like 30-40 MB) because of the debug info that
is included. It's probably gone up since then. Is something that big still
worth the upload/download time?
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
). Would it be possible to write the