Re: [softwerk-dev] new release, plus "manual": SUCCESS!

[Paul Barton-D. <pb...@op...>]

>I think you're right. 'echo $LD_LIBRARY_PATH' yields nada, if that tells
>us anything useful.

tremendously useful. thats precisely the problem. the libraries are
installed "locally", so ldconfig doesn't help ld to find them. the
plan is for it to use LD_LIBRARY_PATH, which was set by configure, but
not exported. presto - it doesn't work.

>Yes, but I thought it applied only to a CVS build. My bad.

its there for both.
 
>I still haven't tested it, but it's on today's menu. I must say it looks
>*great*, quite an advance from the old XForms version (which I remember
>fondly).

heh. wait till you try to adjust the step values. i'll probably try
and fix this during the day today.

>Btw, can I safely assume that the libs from this build are usable if I
>decide to take another swipe at Ardour ? 

absolutely. but it won't be easy using them. you've installed the
libs themselves in /usr/lib, but not the rest of the stuff (the m4
files, in particular). 

so, here's what to do. below is a patch for the configure
script. apply this patch. then remove the libraries you copied to
/usr/lib. then try a rebuild. assuming this works (it should), you
will then have a set of libraries ready to use. you can do two things:

     1) link the libs dir of ardour to the libs dir of softwerk
     2) delete the ardour libs tree; copy the libs tree of softwerk to
            the ardour source tree

stay in touch,
--p

ps. this patch has been applied to CVS.

--- configure.in        2000/11/28 04:46:58     1.9
+++ configure.in        2000/11/28 16:04:40
@@ -55,6 +55,12 @@
 PATH=libs/bin:$PATH
 LD_LIBRARY_PATH=libs/lib:$LD_LIBRARY_PATH
 
+dnl some people don't have LD_LIBRARY_PATH set as an environment
+dnl variable, and so we must force this to be exported in order
+dnl that ld(1) can use it.
+
+export LD_LIBRARY_PATH
+
 LIBS="-Llibs/lib $LIBS"
 CXXFLAGS="-Ilibs/include $CXXFLAGS"