[Nexus-developers] NeXus makefiles

[Akeroyd, FA (Freddie)]

If a split shared library is activated 
dynamically at run time, loading e.g. libNeXusF77.so/libNeXusF77.dll would
automatically attempt 
to load libNeXus.so/libNeXus.dll. The complication is in the directory the
program 
will search for the referenced library (libNeXus) - in some cases the
directory in 
which libNeXusF77 was found will not be automatically searched unless it is
specified in the 
(Unix) LD_LIBRARY_PATH / (Windows) PATH    environment variable. Though it
is unlikely the
fortran bindings would get loaded this way, the e.g. python bindings will
and hence the
NeXus install kit may need to take care to set the appropriate variables /
make necessary
file links. 

Regards,

Freddie
 
> -----Original Message-----
> From: Peterson, Peter F. [mailto:petersonpf at ornl.gov]
> Sent: 28 October 2003 15:39
> To: nexus-developers at anl.gov
> Subject: RE: [Nexus-developers] NeXus makefiles
> 
> 
> How does organizing the static libraries affect shared libraries?
> Specifically, java and idl normally would use the NAPI 
> through a shared
> library built using the c-code. However, I prefer Freddie's suggestion
> of keeping the c-library out of the other libraries and require that
> both be included when compiling.
> 
> P^2
>