>> I'm trying to build an add-on module (for an Oracle interface) and
>> having some trouble getting it to build.
> I recommend using a separate build directory - do not build in src/!
> $ mkdir modules/oracle
> ...
OK thanks for the tips. I'll give it a whirl. It's been pointed out
I could do something like auto-detection of the Oracle environment
that is used in the equivalent module they have in the perl ("DBD").
> note that CLISP is under GPL which means that _IF_ you distribute
> your code, it _MUST_ be distributed under the GPL.
>
> would you like us to distribute your module with CLISP?
No problem on all counts.
But let me get it built first, and running on a few Unixen :)
I have a few potential volunteers to eventually test it on: Linux,
Solaris and SGI Irix.
thanks; keep you posted.
---
John Hinsdale, Alma Mater Software, Inc., Tarrytown, NY 10591-3710 USA
hin@... | http://www.alma.com/staff/hin | +1 914 631 4690

> * In message <200207021522.g62FMobR028428@...>
> * On the subject of "[clisp-list] Building add-on module"
> * Sent on Tue, 2 Jul 2002 11:22:50 -0400
> * Honorable "John K. Hinsdale" <hin@...> writes:
>
> I'm trying to build an add-on module (for an Oracle interface) and
> having some trouble getting it to build.
>
> The notes in the generated Makefile say to make a subdir of the src/
> directory w/ the same name as the module, and I've done all that, and
> also created the necessary .lisp interface, etc. All my "C" files and
> .lisp interface file compile fine in isolation.
I recommend using a separate build directory - do not build in src/!
> What I really like to do is be able to just build a single "full"
> distribution w/ all the other modules (regex, wildcards, OS calls) as
> well as my Oracle module.
$ mkdir modules/oracle
$ mv .... modules/oracle
$ ./configure --with-module=oracle --build build-dir
if you want to rebuild,
$ cd build-dir
$ rm -rf full
$ make
> The docs (again notes in the Makefile - out of date?) say to create a
> Makefile (either by hand or generated by autoconf) specific to my
> module.
it also recommends 'rm rf full'.
> 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.
> Any ideas? One way I can force it work is to edit the generated
> Makefile by hand, but I would like to avoid that. My ultimate goal is
> to be able to distribute to interested parties a directory that they
> can graft right onto their CLISP distribution for a build that would
> include the Oracle package.
note that CLISP is under GPL which means that _IF_ you distribute your
code, it _MUST_ be distributed under the GPL.
would you like us to distribute your module with CLISP?
--
Sam Steingold (http://www.podval.org/~sds) running RedHat7.2 GNU/Linux
<http://www.camera.org&gt; <http://www.iris.org.il&gt; <http://www.memri.org/&gt;
<http://www.mideasttruth.com/&gt; <http://www.palestine-central.com/links.html&gt;
Those who can laugh at themselves will never cease to be amused.

I'm trying to build an add-on module (for an Oracle interface) and
having some trouble getting it to build.
The notes in the generated Makefile say to make a subdir of the src/
directory w/ the same name as the module, and I've done all that, and
also created the necessary .lisp interface, etc. All my "C" files and
.lisp interface file compile fine in isolation.
What I really like to do is be able to just build a single "full"
distribution w/ all the other modules (regex, wildcards, OS calls) as
well as my Oracle module.
The docs (again notes in the Makefile - out of date?) say to create a
Makefile (either by hand or generated by autoconf) specific to my
module. That's good, as I have compilation things specific to Oracle
such as where to get its headers and link libs. However when I run
the "makemake" with --with-module=oracle it generates a build that
appears to ignore my Makefile and use a general set of compilation
flags.
I've also noticed when working w/ a toy-addon that the Makefile
generated by "clisp-link create-module-set" also seems to get ignored.
I'd like to avoid a solution that requires me to distribute Oracle's
header files as I will then have compatibility and license issues.
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.
Any ideas? One way I can force it work is to edit the generated
Makefile by hand, but I would like to avoid that. My ultimate goal is
to be able to distribute to interested parties a directory that they
can graft right onto their CLISP distribution for a build that would
include the Oracle package.
---
John Hinsdale, Alma Mater Software, Inc., Tarrytown, NY 10591-3710 USA
hin@... | http://www.alma.com/staff/hin | +1 914 631 4690

Community

Help

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. I understand that I can withdraw my consent at any time. Please refer to our Privacy Policy or Contact Us for more details