Difference between revisions of "Extension requirements"
Jump to navigation
Jump to search
(Updated the status of Python) |
|||
| Line 22: | Line 22: | ||
=== on Mac OS X === | === on Mac OS X === | ||
Starting with version 0.46, Inkscape contains the python packages needed for the extension system. All python extensions should work out of the box. However in case you still have trouble you can install them in their regular location. | |||
==== Binary packages ==== | ==== Binary packages ==== | ||
# Download and open http://inkscape.modevia.com/macosx-snap/Python-packages.dmg | |||
# Browse the disk image to find the packages corresponding to your architecture and Python version | |||
#* Your architecture is ppc if you have a G4-G5 based Mac, i386 if you have an Intel Mac | |||
#* By default Panther and Tiger have Python 2.3 and Leopard has Python 2.5. If you have installed a newer version of Python we also provide packages for 2.4 | |||
# Copy all the files and folder from the appropriate location to your Python site-packages directory. By default the site-packages directory is /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages on Panther and Tiger, /Library/Python/2.5/site-packages on Leopard. Otherwise it is somewhere in your custom install of python (/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/ for and install of Python 2.4 via MacPorts for example) | |||
==== Compiling from source ==== | ==== Compiling from source ==== | ||
If you prefer, you can install them from source, it is really easy. | If you prefer, you can install them from source, it is really easy. | ||
# download the source code | # download the source code for [http://sourceforge.net/project/showfiles.php?group_id=1369&package_id=175103 sourceforge numpy repository] and/or [http://codespeak.net/lxml/index.html#download lxml download section] | ||
# unpack the <code>.tar.gz</code> file <pre>tar -xzf numpy***.tar.gz lxml***.tar.gz</pre> | # unpack the <code>.tar.gz</code> file <pre>tar -xzf numpy***.tar.gz lxml***.tar.gz</pre> | ||
# for each one <code>cd<code> into the newly created directory | # for each one <code>cd<code> into the newly created directory | ||
# build C extensions and install (the install is system wide so you need administrator | # build C extensions and install (the install is system wide so you need administrator privileges)<pre>sudo python setup.py install</pre>and type your password. | ||
The packages are installed in the <code>site-packages</code> directory of your Python install. This is <code>/Library/Python/2.*/site-packages/<code> for the stock install of Python on Mac OS X. | The packages are installed in the <code>site-packages</code> directory of your Python install. This is <code>/Library/Python/2.*/site-packages/<code> for the stock install of Python on Mac OS X. | ||
Revision as of 19:07, 19 February 2008
Setting Up Effects in Inkscape
For effects to work you need to be using inkscape .42 or later.
For info about what effects can do, screenshots, and how to make your own go to Aarons Site
See also GettingExtensionsWorking.
(Only necessary in some versions of Inkscape. Between .41 and .45)
On the "Misc" tab of the "Inkscape Preferences" dialog check the box labeled "Enable script effects" (0.41+CVS onwards only)
Close and reopen Inkscape
Python Effects
on Debian GNU / Linux
apt-get install python python-xml
on Microsoft Windows
GettingEffectsWorking/Windows Tutorial on Getting Effects to work on Windows
on Mac OS X
Starting with version 0.46, Inkscape contains the python packages needed for the extension system. All python extensions should work out of the box. However in case you still have trouble you can install them in their regular location.
Binary packages
- Download and open http://inkscape.modevia.com/macosx-snap/Python-packages.dmg
- Browse the disk image to find the packages corresponding to your architecture and Python version
- Your architecture is ppc if you have a G4-G5 based Mac, i386 if you have an Intel Mac
- By default Panther and Tiger have Python 2.3 and Leopard has Python 2.5. If you have installed a newer version of Python we also provide packages for 2.4
- Copy all the files and folder from the appropriate location to your Python site-packages directory. By default the site-packages directory is /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages on Panther and Tiger, /Library/Python/2.5/site-packages on Leopard. Otherwise it is somewhere in your custom install of python (/opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/ for and install of Python 2.4 via MacPorts for example)
Compiling from source
If you prefer, you can install them from source, it is really easy.
- download the source code for sourceforge numpy repository and/or lxml download section
- unpack the
.tar.gzfiletar -xzf numpy***.tar.gz lxml***.tar.gz
- for each one
cdinto the newly created directory - build C extensions and install (the install is system wide so you need administrator privileges)
sudo python setup.py install
and type your password.
The packages are installed in the site-packages directory of your Python install. This is /Library/Python/2.*/site-packages/ for the stock install of Python on Mac OS X.
Perl Effects
on Debian GNU / Linux
apt-get install perl libxml-xql-perl
on Gentoo GNU / Linux
emerge -a XML-XQL
on Microsoft Windows
install ActivePerl
install XML::XQL::DOM (perhaps like this?)
1: install prereqs with ppm:
install xml-dom
install parse-yapp
install datemanip
2: download xml-xql from:
http://www.cpan.org/authors/id/T/TJ/TJMATHER/XML-XQL-0.68.tar.gz
3: open command prompt and locate perl"s lib directory with:
perl -e "print qq(@INC)" (mine was C:/Perl/site/lib)
4: unpack xml-xql archive
5: copy contents of XML-XQL-*\lib\XML into C:\Perl\site\lib\XML
6: copy XML-XQL-*\XQLParser\Parser.pm to C:\Perl\site\lib\XML\XQL
Plugin Effects
I have absolutely no idea. Please record your success here. :)
What if it doesn't work?
Run Inkscape from the console
Use the error messges printed to the console to diagnose the problem (very often missing dependencies)
On Windows you will have to redirect output to a text file like this: "inkscape > output.txt"