[reportlab-users] Reportlab compiling in Linux
andy at reportlab.com
Wed May 2 17:02:57 EDT 2007
On 02/05/07, Uwe C. Schroeder <uwe at oss4u.com> wrote:
> The only change to the original is the sys.path.append statement.
> The path to append would be the lib directory in the build. It's certainly
> important that the sys.path.append statement is before the import reportlab
> statements :-)
I was out today but was going to point out that your sysadmin probably
had his Python path set up wrong.
Uwe is right, there's no reason you can't do everything on your own
user account - as long as the C compiler is available. I have
worked on many weird machines at client sites where it wasn't in a
standard place, or needed special environment variables setting up -
usually Java shops where compiling C code is unusual or a forgotten
skill, or where some security cop has decided to limit what users can
do in a brutal way. If "setup.py build" works, you're fine; if not
we'll be able to help with the next step or possibly to get the one or
two C libraries built elsewhere.
Once you get this working you will also have proof that the sysadmin
is either being unhelpful, or doesn't know what a Python package is.
More information about the reportlab-users