#530 Additional paths for @INC does not work

v0.6.x
open
nobody
Core (65)
5
2009-01-06
2009-01-06
No

Hello,

I have got the following:

Y:\Eclipse\<project>\trunk\<code>\lib\

In code is e.g a file which mentions use lib::Foo.

Now lib::Foo has a use on lib::Bar (which is valid) but it does not work, epic shows me errors from Perl. This comes because of it is validating Bar and Foo in the lib directory and then it surely can not find lib::Bar.

Now I added like it stands in the FAQ some props (include paths) like: ../, Y:\Eclipse\<project>\trunk\ etc etc, but it does not work.

e.g:
Description Resource Path Location Type
Can't locate conf/Settings.pm in @INC (@INC contains: C:/Perl/site/lib C:/Perl/lib .) Database.pm Streamplus v3/trunk/system/lib line 8 Perl Problem

It also dies not show me the addition include paths.

Discussion

  • Jan Ploski

    Jan Ploski - 2009-01-07

    1) After changing project's @INC via properties, always do Project/Clean...
    2) Based on your description, the only path that you should add to @INC is the project-relative "trunk/<code>" (slash, not backslash, mind you).
    3) Let me know whether the additional include path doesn't appear in the error messages after "Project/Clean" or when you run a test script

    foreach $i(@INC) { print "$i\n"; }

     
  • Patrick Matthäi

    Hmm I tried it out with the full path to <code> and just with the relative trunk/<code> and also do a project/clean, but it does not help.

    Now I just get errors like these:

    Description Resource Path Location Type
    Compilation failed in require ConfWriter.pm <project>/trunk/system/lib line 8 Perl Problem

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks