I have custom perl library directories in my project and I would like to include them on the perl include path (to avoid the dreaded syntax errors on the package import lines). I tried just adding a -I<libdir> to the perl executable specification, but that didn't seem to work. Which obvious thing am I missing?
It should work like this.
It does not work (at the moment) if the include path contains spaces.
We are working on that.
That's strange. So, "perl -I/careersite/jobcenter/lib" should work as a executable specification?
BTW, if you have need of another set of hands for software help, I'd love to get involved in this.
In the 4-24 build using 'perl -I/path/to/lib' as the perl executable works (without even having to specify the project include path).
Log in to post a comment.