Hi Kay,
Thanks for reporting this problem. The current version of SetBuildDir does not handle well by passing a relative path. This will be fix very shortly in the CVS repository. But note, that when using (the new) SetBuildDir with a relative pathname, this pathname will be relative to the current directory at the time of __compilation__ (and not at the time of calling SetBuildDir) [Please let me know if this is the __wrong__ interface]
As a work-around use SetBuildDir with a full pathname:
gSystem->SetBuildDir("/path_name_from_the_root/linux_v2.4");
Cheers,
Philippe.
-----Original Message-----
From: Kay Ulbrich [mailto:ulbrich@iskp.uni-bonn.de]
Sent: Thursday, April 24, 2003 7:34 AM
To: roottalk@pcroot.cern.ch
Cc: Philippe Canal
Subject:
Hello Philippe,
thanks for your answer. But there is a problem when doing as you have
told. I set e.g.
'gSystem->SetBuildDir("linux_v2.4");'
As far as I have understood, when the source file for the library is
/home/username/root/lib/libsrc.C, the library then is created as
~/root/lib/linux_v2.4/home/username/root/lib/libssrc_C.so
But when starting root and thus trying to compile the libraries I get
the error message:
Info in <TUnixSystem::ACLiC>: creating shared library linux_v2.4//home/username/root/lib/libssrc_C.so
g++: linux_v2.4//home/username/root/lib/file9sPL7U.cxx: No such file or directory
g++: No input files
g++: linux_v2.4//home/username/root/lib/file9sPL7U.o: No such file or directory
Error in <ACLiC>: Compilation failed!
I did find neither an explanation nor a solution for that.
On Wednesday, April 23, 2003, 10:38 -0500, Philippe Canal wrote:
> Hi Kay,
>
> Use gSytem->SetBuildDir("/somewhere/osname");
>
> See http://root.cern.ch/root/html/TSystem.html#TSystem:SetBuildDir
This archive was generated by hypermail 2b29 : Thu Jan 01 2004 - 17:50:11 MET