Re: [Bitpim-devel] Mac OS X User & Dev page

[Roger B. <ro...@ro...>]

> As for the installer, I would like to have a discussion on this a bit. 
> Particularly, should the goal be to create a monolithic installer for 
> all of the pieces I describe on the site? If so, is it even legal since 
> the pieces come from so many places?

I would prefer that it looks, feels and installs like a normal
Mac application.  This pretty much means it should be monolithic
with no external dependencies.

There should be no legal issues.  See the acknowledgements at the bottom
of http://bitpim.sourceforge.net/readme.html

For Windows, I use py2exe to generate the base runtime code.  The output
is an executable with all the Python files embedded and the Python DLL
seperately.  The executable basically loads the Python DLL and sets itself
up on the import path.  py2exe also finds all other dependent DLLs such
as the ones used for wxWindows and wxPython.

Here is a directory listing:

.:
PyWinTypes22.dll*  bitpim.exe*   python22.dll*  win32event.pyd*  wxmsw24h.dll*
_sre.pyd*          gridc.pyd*    resources/     win32file.pyd*
_winreg.pyd*       select.pyd*    wxc.pyd*

./resources:
unknown.png

(The resources subdirectory contains various toolbar bitmaps etc. but I have only
made unknown so far).

I then use InnoSetup to turn this into a single binary which is the installer.

On Linux I plan for two different installers.  One will be pure RPM and will
have dependencies etc.  The other will be monolithic based on above.  The only
program I have found that works on Linux to help is McMillan installer
http://www.mcmillan-inc.com/install5_ann.html

Roger