Am Freitag 19 März 2010 17:31:17 schrieb Giovanni Bajo: Hi all,
> > I think the problem is that, when you install the app under Windows, you > create a top-level package named "Gnumed". Given the paths that you > quoted: > > c:\workplace\gnumed-0.6.2\client\gnumed.py > c:\workplace\gnumed-0.6.2\client\pycommon\gmPG2 > > there is absolutely no "Gnumed" package here. If you added it, such as: > > c:\workplace\gnumed-0.6.2\client\gnumed.py > c:\workplace\gnumed-0.6.2\client\Gnumed > c:\workplace\gnumed-0.6.2\client\Gnumed\__init__.py > c:\workplace\gnumed-0.6.2\client\Gnumed\pycommon\gmPG2 > > it would probably work out of the box. > I forgot to mention that I tried that as well by creating a symlink on Windows with Mklink. Maybe that does not work. However "running" the package from that directory (unfrozen) works after producing the symlink. I guess I will have to try some more. > Anyway, if you want to setup custom import paths for PyInstaller, you > can modify the "path" variable that is passed to the Analysys() call in > the spec file. That is basically the equivalent of a custom PYTHONPATH > used by PyInstaller. > That is what I figured but it did not seem to work. Guess the problem is on my side and I will have to try some more. Thanks, Sebastian -- 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.
