On Wed, 14 Apr 2010 11:49:57 +0200, Krzysztof Jakubczyk <[email protected]> wrote: > Hi, > I'm writing a program that uses a C++ compiled library and the library > is using boost python. I am doing the following steps: > > Makespec.py --paths src;vs\Release;$(BOOST_DIR)... > Build.py app.spec > > The vs\Release directory contains the compiled library (Library.pyd > file) and the $(BOOST_DIR) contains path to boost dll's that the > library.pyd depends on. The Library.pyd is successfully included in the > pyInstaller distribution but the boost dll is not. It seems that > "--paths" is used to search for source-> binary dependency but not used > to search for binary->binary dependencies. Is that correct?
Yes -- not that I like it. I will eventually remove --paths (and pathex in specfiles). The idea is that Build.py must work out of the box in the same environment that the program itself runs it. So, if you configure PYTHONPATH to run your program, Build.py correctly picks it up. I don't see a good reason for having a special path for PyInstaller only. This said: how do you run your application? How do you setup your environment? How can Library.pid know that $(BOOST_DIR) contains the boost dlls it needs? > PS. > Or maybe somebody knows how can I include dependant dll files when > creating release in visual studio 2008? Because another solution is to > force VS to copy needed dlls to the vs\Release dir. If you're using VS2008 you might want to try PyInstaller's py26 branch, because it correctly handles dependencies between dlls using manifests. -- Giovanni Bajo :: [email protected] Develer S.r.l. :: http://www.develer.com My Blog: http://giovanni.bajo.it -- 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.
