> So this file of course exists, in a different path. Inno
> expected \build
> \bin\lib\site-packages\win32\PythonService.exe and it is in \build\bin
> \lib\site-packages\PythonService.exe
>
> Should I change Inno's reference (have to do that for the b2
> release) or
> should it go into a different
Am Donnerstag, den 26.05.2005, 16:54 +1000 schrieb Mark Hammond:
> PythonService.exe wont match "win*.exe"
Yeah, right. Stupid computers ... ;)
So this file of course exists, in a different path. Inno expected \build
\bin\lib\site-packages\win32\PythonService.exe and it is in \build\bin
\lib\site
> Am Donnerstag, den 26.05.2005, 09:03 +1000 schrieb Mark Hammond:
> > What path does the final Inno file refer to? Is the entire
> > path missing, or
> > just that file missing from that path? IIRC, we explode the pywin32
> > installer and grab the file from there. I'm pretty sure
> > that file
Morning,
Am Donnerstag, den 26.05.2005, 09:03 +1000 schrieb Mark Hammond:
> What path does the final Inno file refer to? Is the entire path missing, or
> just that file missing from that path? IIRC, we explode the pywin32
> installer and grab the file from there. I'm pretty sure that file is in
> Howdy,
>
> The InnoSetup complained about pythonservice.exe to be missing during
> packaging the installer. Any ideas?
What path does the final Inno file refer to? Is the entire path missing, or
just that file missing from that path? IIRC, we explode the pywin32
installer and grab the file fro
Howdy,
The InnoSetup complained about pythonservice.exe to be missing during
packaging the installer. Any ideas?
Cheers,
Christian
--
gocept gmbh & co. kg - schalaunische str. 6 - 06366 koethen - germany
www.gocept.com - [EMAIL PROTECTED] - phone +49 3496 30 99 112 -
fax +49 3496 30 99 118 - zo
