Dear list members,
I have a problem using the MYEXTLIB option with Inline::C.
I am running on RedHat Linux release 9 with Inline 0.44 and
I have put all my external C libraries in a subdirectory named 'lib'.
I have the following code (I just quote the first few lines which are related).
It runs well with the following command "perl foo.pl"
---------------------------------------------------------------------------------
use Cwd qw(cwd);
use Inline C => Config =>
MYTEXTLIB => cwd.'/lib/mylib.so';
..................................................
----------------------------------------------------------------------------------
However, when I moved my foo.pl, the 'lib' subdirectory and the _Inline directory
created to another location and run the script directly (without compiling again),
it fails complaining that it is unable to locate the mylib.so external libraray.
(It remains searching in the 'old' location for the mylib.so -- i.e. suppose the foo.pl
is in /home/project above when it first get compiled, it will remain searching
mylib.so from /home/project/lib --no matter all the stuff (the foo.pl, the lib and the
_Inline directory) is moved to a new location e.g. /home/my/path)
I would like to ask is there a way for me to specify the path in MYEXTLIB as a
'relative' path in the sense that it can automatically discover the current directory
my foo.pl is in and be able to locate the mylib.so and execute properly WITHOUT
having to recompile everytime just because it has been put in a different location?
(actually it is not only the need for recompilation that matters, more important is
that
i could have more flexibility in product deployment as i do not need to specify and
to stick to any absolute path)
Any help would be greatly appreciated.
Thanks
Keith.
---------------------------------
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing
