[Nexus-developers] NeXus & autoconf

[Peterson, Peter F.]

Mark,

At the end of running configure there should be a list of what compilers
it found. By default everything is installed in /usr/local, but if there
is missing library (like the fortran) you can go into bindings/.lib and
it should be there if it was built at all. Compiled libraries do not go
into cvs since they are created during the build process.

BTW: The full dance (after autogen.sh) is 'configure', 'make', 'make
test', 'make install'. Then you can compile anything against the
libraries. The only change I've noticed is now I pass '-lNeXus' to the
linker for C code.

P^2

-----Original Message-----
From: nexus-developers-bounces at anl.gov
[mailto:nexus-developers-bounces at anl.gov] On Behalf Of Mark Koennecke
Sent: Thursday, April 22, 2004 9:10 AM
To: nexus-developers at anl.gov
Subject: [Nexus-developers] NeXus & autoconf



  High,

  I implemented NXopenpath and want to put it back into the cvs. But I
  want to test it first against the sources in the cvs. Unfortunately I 
  cannot get the new autoconf'ed compile to work. I built recent
versions
  of all the tools (Siggghh), ran autogen.sh, configure, make and on the
  compile it is missing files like napif.lo java...la Being blind to the
  inner workings of autotools I would ask for someone to put those files
  into the repository. Or is something else amiss?   

                             Mark




_______________________________________________
NeXus-developers mailing list
NeXus-developers at anl.gov
http://www.neutron.anl.gov/mailman/listinfo/nexus-developers