"Dylan Nicholson" <[EMAIL PROTECTED]> writes:
> Would there be place or purpose to make publically available a version
> of libguile intended for compiling under MSVC?
As far as the core Guile distribution is concerned, I think it depends
on whether there is any practical difference between an MS
Vorfeed Canal <[EMAIL PROTECTED]> writes:
>
> "now what I need to do to
> install guile 1.8.1 as /usr/bin/guile-1.8.1 and guile 1.8.2 as
> /usr/bin/guile-1.8.2"
Install under different $prefix.
> Where configure.ac/Makefile.am
> should put libmysuperextension.la (+ .so, etc) file ?
Under the $pr
Neil Jerram <[EMAIL PROTECTED]> writes:
> Greg Troxel <[EMAIL PROTECTED]> writes:
>
> Yes, thanks. This is exactly what was in my mind too, but I didn't
> make that clear.
Glad I was helpful - was feeling redundant but posted anyway.
> Basically, when I'm using a distribution (Debian in my cas
Greg Troxel <[EMAIL PROTECTED]> writes:
> I concur with most of your comments, but would like to make a
> metapoint: various OS/distributions/packaging systems have rules about
> what goes where, and guile should be such that it can be made to
> behave 'right' for these varying definitions of righ
INSTALL file explains how this information is supposed to be delivered
to libltdl (with LD_LIBRARY_PATH). No information about how this
information is supposed to be found by configure.ac/Makefile.am in
extension. Neither in documentation of guile nor in code of existing
extensions.
IM
On 10/9/05, Kevin Ryde <[EMAIL PROTECTED]> wrote:
> Vorfeed Canal <[EMAIL PROTECTED]> writes:
> >
> >> GUILE=/myexperiments/guile/bin/guile \
> >> GUILE_CONFIG=/myexperiments/guile/bin/guile-config \
> >> GUILE_TOOLS=/myexperiments/guile/bin/guile-tools \
>
> I would set the PATH, this probably wor
