Re: [clisp-list] Building add-on module

[John K. H. <hi...@al...>]

   >> * Sent on Tue, 2 Jul 2002 11:22:50 -0400
   >> * Honorable "John K. Hinsdale" <hi...@al...> writes:
   >> 
   >> I'm trying to build an add-on module (for an Oracle interface) and
   >> having some trouble getting it to build.

 > Date: 02 Jul 2002 12:25:39 -0400
 > From: Sam Steingold <sd...@gn...>
 > I recommend using a separate build directory - do not build in src/!
 > $ mkdir modules/oracle
 > $ mv .... modules/oracle
 > $ ./configure --with-module=oracle --build build-dir

   >> What I really want is to be able to say (somewhere, anywhere) where to
   >> get those headers and libs, but it is not obvious to me where.

 > your best bet is to use autoconf for this.

OK, I've set all this up properly, incl. the module dir suitable for
eventual distribution and an autoconf-generated Makefile that has
everything needed to compile my stuff, yet the CLISP build is _still_
ignoring my Makefile and I have no idea why.

I did everything Sam suggested, e.g., w/ autoconf and a separate build
dire ("mysrc") and in fact the build _is_ running my "configure" when
it sees it.  I see my "configure" generates the desired Makefile; but
then when it comes time to compile my "C" sources my Makefile is not
used -- instead the build uses a gcc command appearing in the parent
directory's Makefile.

Any ideas?  Perhaps my problem may be due to how I've set up the
"link.sh" which I am not quite clear on its role.  The docs say it is
to set some make/environment variables, however I notice that the
link.sh in all the other modules contain a "make clisp-module" and I
assumed I had to do that as well.  But shouldn't it use my module's
Makefile?  Otherwise what is the point of creating it?

Any help would be greatly appreciated.  I've got all this code and no
Lisp to run it(!).

You can peek at my build area at: http://hinsdale.net/clisp-2.28/
The Oracle module is in http://hinsdale.net/clisp-2.28/modules/oracle/
and the build command I'm using is: http://hinsdale.net/clisp-2.28/doconf
with output: http://hinsdale.net/clisp-2.28/doconf.log

My next step is to wade into the source for the build environment in
detail, but before I do that I was hoping someone would eyeball it for
some obvious problem.

---
John Hinsdale, Alma Mater Software, Inc., Tarrytown, NY 10591-3710 USA
hi...@al... | http://www.alma.com/staff/hin | +1 914 631 4690