On Mon, Mar 2, 2009 at 6:08 PM, yvesm <[email protected]> wrote: > > Florent : > > Thanx for the links. I'm not sure I want to use a totally different > approach (than NSIS) to packaging for windows just to setup TG. My > installer installs a bunch of other things and my understanding is > that it would add complexity to the NSIS installer to use pylunch for > bits of it, but I may be wrong. I'll report on my trials.
I actually am pre NSIS If I may says so :) If you look into pylunch you'll see an small NSIS script. Just adapt it to your needs and from the command line you can type: python setup.py py2exe nsis even if you don't want to use pylunch, the way I integrate NSIS inside a distutils command to automate the installer creation can be helpfull to you ;) I would sat pylunch is just sugar on py2exe, it does not replace NSIS nor py2exe in any way, it just helps to industrialize the build process, to make it repeatable whatever the machine (ever used py2exe on 2 different machines and got 2 different libs pulled in the exe?) Florent. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
