jiho wrote:
If you could correct the wiki page that would be even better.
Yeah I just ran sudo port install gtk2-clearlooks and all the other dependant libs I found in the pre-packaged nightly. I will try to build again later on and see if they get copied to the engines subdir of the .app bundle automatically. I will also try to update the wiki later this weekend.
jiho wrote:
For python, you are indeed required to compile the two libraries/ packages Inkscape uses separately. Then there is an option to the build script which tells it where to look for these packages so that it can include them in the bundle. There are also precompiled python packages on Modevia, but probably not for Python 2.6.
Ah I see. I did not know about Modevia thanks for mentioning it. Are you talking about the --with-python option? or a --with-PACKAGE option?
jiho wrote:
That hardcoded, non-standard PYTHONPATH is meant to ease the distribution of Inkscape. For releases we ship a universal, multi- architecture, multi-system (well, at least it is meant to be multi- system) version of Inkscape so we need the python librairies to match all those possibilites. So we ship everything, for PPC and intel, for different versions, in several directories within this strange path. If you think of a better solution to this problem, it would be welcome.
Nope at the moment I can't think of a better way. You ultimately need a dir to put all the dependant stuff in if you want to ship it Python batteries-included style.
jiho wrote:
If that can be done for release versions also, it would be nice. If it is for personal/development versions only, then I am not sure I like it. Because ultimately, dev builds are a way to test things for the release and if they function in a different way, it defeats their purpose.
The second method should always work as I understand that every in-program effect is launched trough inkex.py and that file is inside the extensions dir. So if it requires "from lxml import etree" and has a lxml directory with a etree.py file it can import it directly (w/o searching PYTHONPATH) as requested. Of course if a Python interpreter is not included with inkscape the user still needs to habe the correct version of Python installed which must equal the Python version that was used to precompile the module.
jiho wrote:
I hope you'll find the solution to all your problems. If you can post your new builds on Modevia, it will help other people that are not willing to enter the whole process of building things but still want to test the new features. Ask around on this list to be given access.
At the moment my build is not very useful outside my own computer. It is not Universal Binary and features only support for Python 2.6 and the average Leopard user has 2.5.1 But if I manage to get a Universal Binary working I will try to post it.
Thanks for tuning in...
André