Support for custom library directories

[GoogleCodeExporter]

Currently, interfacing with custom C++ code requires placing custom .?pp-files 
into shedskin "lib/" directory. This may be problematic if the user doesn't 
have write access to that directory, which is often the case in a system-wide 
installation if shedskin. It also makes sense to keep the project code together 
without the requirement of copying files anywhere.

Attached is a patch that adds a command-line argument to shedskin (-L <dir>), 
which gives a directory to look for "library files".

This, for example, allows running shedskin for the "rsync.py" example right in 
the examples directory as "shedskin -Llib rsync.py"

Original issue reported on code.google.com by art...@gmail.com on 12 Sep 2011 at 1:44

Attachments:

• 0001-add-support-for-custom-library-directories.patch

[GoogleCodeExporter]

thanks a lot for the patch! it's much appreciated.

the patch looks quite clean and sensible, and 'shedskin -Llib rsync' sure looks 
nice. test 148 broke though, but that was easily fixed. another thing that 
seemed to be missing was a '-I..' in the makefile, but that was also easy to 
add. so I committed your patch with these changes.

an extension may be to make the command-line option implicit if there exists a 
'lib' dir locally, similar to the FLAGS file.

if you like, please update the documentation wiki. otherwise I will get to that 
at some point before 0.9.1.

Original comment by mark.duf...@gmail.com on 13 Sep 2011 at 7:07

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by mark.duf...@gmail.com on 23 Nov 2011 at 1:42

• Added labels: milestone-0.9.1

[GoogleCodeExporter]

I updated the wiki. thanks again for the patch!

Original comment by mark.duf...@gmail.com on 16 Dec 2011 at 10:19

• Changed state: Done