On Mar 2, 1:58 pm, Florent Aide <[email protected]> wrote:

> 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 found the NSI script, but I've never done this before so I'll have
to investigate how it benefits me.  Meanwhile, I found a way to have a
complete venv from an NSIS call :

ExecWait '"$INSTDIR\Python25\Scripts\virtualenv" --no-site-packages .
\TileCache'

works as far as the current directory in NSIS is defined by
SetOutPath.  This is equivalent to :

ExecWait ' "$INSTDIR\Python25\Scripts\virtualenv" --no-site-packages
"$INSTDIR\TileCache" '

Except that last line does not work.

I thought the next step for me would be to download the eggs to some
local directory and run easy_install on that directory.  I thought I
could download TG from the internet once and shove the egg files in a
directory for inclusion into NSIS.  I'm not clear on what .egg files
to put there now looking at what I got from the internet download :
egg/zips and .egg.  I'll find out.

>
> 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?)

Thanx for your tips.  It's just over my head for now.  Never used
py2exe ;-).

Yves
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to