Now that I know my SWIG dtor fix was a sound decision ;-), I'm gearing up to create an experimental "wxPython with wxMozilla" release to see how it fares in the wild. I'll probably confine it to Windows only at this point, just because even though the software is cross-platform, the process for building installers and makefiles is not. (Tools like cmake and tmake are starting to look VERY tempting...)
So my question is: How is wxPython's Windows installer built at present?
I played around with the various scripts in \distrib, and also tried using distutils but haven't been successful thus far. Before I tried to go any further on this, I thought I should first ask which method I should be using.
Also, one related question to generating installers. Until I can figure out this dynamic loading business for Mozilla, on Windows at least I will need to add the GRE location to the user's PATH environment variable. (The GRE contains all the Mozilla DLLs and other files.) Is this considered a major no-no? I know it's not preferable, but I would be sure to add a note about it, of course. Any other solution would require DLLs to be distributed with wxPython and raise the package size by at least 2 MB. Thoughts?
Thanks,
Kevin
P.S. for anyone who is interested, the real problem with dynamically loading Mozilla is the Netscape Portable Runtime. It is used internally by Mozilla to load helper DLLs, deal with memory allocation and threads, and do a bunch of other things. It's a large library (it has a 30 chapter manual on Mozilla.org) so I don't think any dynamic loading code will be trivial, especially since the NSPR is used extensively within Mozilla. (All approaches to dynamic loading I've seen require you to manually load each function you want to use.) I may take on this challenge one day, but right now my focus is on getting something that's usable for my own application, and hopefully for others' as well!
So my question is: How is wxPython's Windows installer built at present?
Run the distrib/make_installer.py script. It builds some script files for InnoSetupExtensions and then runs it to make the installer. You can get ISX from Home | Alles op de rit | Beedr, I am currently using version 2.0.18. I don't know if make_installer.py will be compatible with 3.x yet...
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I've been playing with it, and it's looking like the answer is no. So far, the AlwaysCreateUninstallerIcon and CodeFile options are giving "undefined directive" errors. I think what I'll do is create a make_installer3.py script and see if I can get these issues resolved.
Thanks,
Kevin
···
On Tuesday, March 18, 2003, at 10:25 PM, Robin Dunn wrote:
Kevin Ollivier wrote:
So my question is: How is wxPython's Windows installer built at present?
Run the distrib/make_installer.py script. It builds some script files for InnoSetupExtensions and then runs it to make the installer. You can get ISX from Home | Alles op de rit | Beedr, I am currently using version 2.0.18. I don't know if make_installer.py will be compatible with 3.x yet...
So my question is: How is wxPython's Windows installer built at present?
Run the distrib/make_installer.py script. It builds some script files for InnoSetupExtensions and then runs it to make the installer. You can get ISX from Home | Alles op de rit | Beedr, I am currently using version 2.0.18. I don't know if make_installer.py will be compatible with 3.x yet...
I've been playing with it, and it's looking like the answer is no. So far, the AlwaysCreateUninstallerIcon and CodeFile options are giving "undefined directive" errors. I think what I'll do is create a make_installer3.py script and see if I can get these issues resolved.
Or I can send you the 2.0.18 version...
···
On Tuesday, March 18, 2003, at 10:25 PM, Robin Dunn wrote:
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
On Wednesday, March 19, 2003, at 11:15 PM, Robin Dunn wrote:
Kevin Ollivier wrote:
On Tuesday, March 18, 2003, at 10:25 PM, Robin Dunn wrote:
Kevin Ollivier wrote:
So my question is: How is wxPython's Windows installer built at present?
Run the distrib/make_installer.py script. It builds some script files for InnoSetupExtensions and then runs it to make the installer. You can get ISX from Home | Alles op de rit | Beedr, I am currently using version 2.0.18. I don't know if make_installer.py will be compatible with 3.x yet...
I've been playing with it, and it's looking like the answer is no. So far, the AlwaysCreateUninstallerIcon and CodeFile options are giving "undefined directive" errors. I think what I'll do is create a make_installer3.py script and see if I can get these issues resolved.
While trying to build a wxPython installer using the make_installer.py
script, I noticed it is looking for wx.chm and ogl.chm, which aren't
included in the source distros for wxWindows and wxPython. I can of course
copy these files from my current wxPython installation or from the wxMSW
package, but I was curious if there is some script or automated process for
building these docs. I saw some Unix scripts for making ZIP files of the
help docs, but nothing for HTML Help.
While trying to build a wxPython installer using the make_installer.py
script, I noticed it is looking for wx.chm and ogl.chm, which aren't
included in the source distros for wxWindows and wxPython. I can of course
copy these files from my current wxPython installation or from the wxMSW
package, but I was curious if there is some script or automated process for
building these docs. I saw some Unix scripts for making ZIP files of the
help docs, but nothing for HTML Help.
For what you are attempting it would definitly be easier to just copy the .chm's that you already have.
To build the docs yourself you need to build tex2rtf in wxWindows/utils and put it on the PATH, and then install a copy of MS HTMLHelp Workshop and make sure that it is on the PATH so the command line tools can be found. Then in the wxWindows/src/msw do "nmake -f makefile.vc htmlhelp" (or something like that.)
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Hmmm... I think I like the copying option. Copying's good. =) This is actually very useful, though, as I will need to write up some docs for wxMozilla, which I should probably try to do in the TeX format.
I have managed to successfully make a binary, BTW. I've also got the wxMozilla GRE installer running smoothly. The next step will be to add in the wxMozilla files to the wxPython installer package and rebuild. After that, I should be ready to try it on an unsuspecting Windows machine, which will probably break everything and send me back to the drawing board. ^_- Will keep you posted!
Thanks,
Kevin
···
On Friday, March 21, 2003, at 05:04 PM, Robin Dunn wrote:
Kevin Ollivier wrote:
Hi all,
While trying to build a wxPython installer using the make_installer.py
script, I noticed it is looking for wx.chm and ogl.chm, which aren't
included in the source distros for wxWindows and wxPython. I can of course
copy these files from my current wxPython installation or from the wxMSW
package, but I was curious if there is some script or automated process for
building these docs. I saw some Unix scripts for making ZIP files of the
help docs, but nothing for HTML Help.
For what you are attempting it would definitly be easier to just copy the .chm's that you already have.
To build the docs yourself you need to build tex2rtf in wxWindows/utils and put it on the PATH, and then install a copy of MS HTMLHelp Workshop and make sure that it is on the PATH so the command line tools can be found. Then in the wxWindows/src/msw do "nmake -f makefile.vc htmlhelp" (or something like that.)