This is the mail archive of the guile@cygnus.com mailing list for the guile project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Announce: guile-dblib-0.9 available (beta software)



> I've added support for two to non-inuitive configure features.  The
> first of these is called 'dblib', and you can use it to specify where
> your dblib installation is at.  The second of these is called simply
> 'guile', and it is used similarly, to specify where you have guile
> installed.  If you've got guile installed in /usr/local, and
> /usr/local is in your path, then you shouldn't need this to build.
> 
> To build in my installation, I configured like this:
> 
> ./configure --enable-guile=/opt/guile --enable-dblib=/opt/sybase


Maybe I'm misunderstanding, but:

When I run dblib's configure script, does --enable-dblib=PATH tell
dblib where to install itself?  If so, why don't you use --prefix=PATH
instead?

I think you don't need --enable-guile=PATH either.  The configure.in
file should use the GUILE_FLAGS macro, in guile-core/guile.m4; that
is meant give you the CFLAGS and LDFLAGS you need to link against Guile.
It works by running the guile-config program, which must be in your
path.


The thing is, your package is not unusual; if you need weird,
nonintuitive configure options, everyone else writing a Guile package
will too.  So this is very much something for us to work on until it
goes smoothly.  I'm interested in changing Guile as necessary to make
this possible.