Re: [Bitpim-devel] adding py file to windows build?

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

> it's an import, but it's in an if statement.  Is that a problem?

It shouldn't be.

I recommend you change around line 973 of gui.py to be like this:

   if usingvx10:
        import com_lgvx10 as thephone
   elif usingvx4400:
        import com_lgvx4400 as thephone
   else:
        raise some sort of error

   try:
        self.commphone=thephone.Phone(self, comport)
   except Exception,_:
        comport.close()
 
> dunno, just was seeing how it was done.

Ok, here is the full description.

The help is authored using HelpBlocks.  The files it maintains
are in Microsoft HTML Help project format.  It invokes the 
Microsoft Help Compiler to produce the HTML Help format file
(bitpim.chm).  It builds the wxWindows help format itself.  This
format is actually just a zip file of the help project and
named bitpim.htb.

On Windows I currently ship both files.  The help link in the 
start menu points to the CHM file.  BitPim when running uses
the wxWindows help file.  This is because wxPython doesn't
wrap the CHM help controller.  There is a strong chance it will
be in the next wxPython release, at which point the Windows 
version of BitPim will ship with only the CHM.

The build process invokes some of my files first.  The main one
turns the helpids into generated code (helpids.py).  It then
asks HelpBlocks to build the help.  HelpBlocks actually has
a builtin macro processor, so it rebuilds all the HTML source
files, and then invokes the Microsoft Help Compiler to make
the CHM and builds the HTB itself.

py2exe is then used to make the Windows executable, grab the
associated DLLs etc.

I use Resource Hacker to add an icon to the executable.

Finally InnoSetup is used to produce the installer.

On Linux, I use the help file committed into CVS, and use 
cx_Freeze to produce a binary and associated shared libraries.
Finally my own rpm spec file is used to produce the RPM from
those files.

Roger