On Feb 1, 6:03 pm, Giovanni Bajo <[EMAIL PROTECTED]> wrote:
> On 2/1/2007 5:23 PM, schu wrote:
>
> > I wanted to use the non-ELF strategy on Windows, i.e. to have a
> > executable.pkg archive next to the executable. I have set 'useELFEXE':
> > 0 in config.dat. But if I run Build.py I get the following output/
> > traceback:
>
> This is not supported under Windows, as far as I know. The term "ELF"
> always meant "not for Windows" for me.
>
> Why would you want to keep the .pkg file external?
There are mainly 2 reasons:
1) I want to keep the installation the same on Windows and Solaris
(though I'm not yet a 100% sure that I have to use non-ELF on Solaris)
2) It's not the standard Python that will call all my scripts but for
some scripts it's a third party product. I hoped to be able to use
PyInstaller to create me a zip file I could ship with the
installation. A bit more concrete:
It's not
> python myscript.py
I want to replace with an exe
but
> their_exe myscript.py
So I wanted to create a myscript.exe but just use the myscript.exe.pkg
in the import path. So I could still use:
their_exe myscript.py
and set the pythonpath to myscript.exe.pkg at the very beginning of
myscript.py.
Regarding point 2): I'm not even sure if I could use the package file
in the pythonpath with the standard python import statement. Would
this work?
I know that this might all sound a bit strange. But believe me there
are some good reasons.
--
Andy Schumann
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"PyInstaller" 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/PyInstaller?hl=en
-~----------~----~----~----~------~----~------~--~---
