17 Sep
2004
17 Sep
'04
11:56 a.m.
Dave Phillips wrote:
Greetings:
All of this points up why I wish the tutorials were wiki-ized. The fst
1.6 package has not been repaired, even though I sent a notice to the
developers quite some time ago. I certainly deplore the existence of
misleading information as much as anyone else, but I simply can't keep
up with things like this anymore.
Don't worry about it too much I'll first try to implement Luke's
instructions for fixing this or I'll drop back to fst_1.5.
I'm sorry for wasting your time, Mark, and I hope you get things
operational despite my instructions. ;) I know how it feels: yesterday
I spent an hour compiling xine for my laptop, only to find that the UI
wouldn't build unless I used a newer version of the library. Grrr...
Yesterday was no worse than others. The instructions were actually VERY
helpful. My only input was on the fixheaders step change the instructions to
cd vst
../fixheaders
cd ..
and that will be taken care of. This step was documented in some other
readme file somewhere.
BTW - How could I ever get disappointed with you for all the great stuff
you put on the web?!?! You're stuff is, overall, really amazing. I'd be
lost without it! Where the real responsibility lies, looking at the
software IP products my company delivers as a model, is with the
developers and packagers. Everyone includes a README. Some include an
INSTALL. In many/most cases they seem to go out unmodified from Gnu and
cause more wasted time than help. Cheers to all the developers that
write their own README and INSTALL docs and make this work better.
Luke, if you or anyone else can supply me with updated
compile/installation/configuration details for libfst or the vstserver
I'll do one more update on the tutorial. Please try to point out where
my tutorial is failing for you and I'll make the necessary changes.
Best regards,
dp
Luke Yelavich wrote:
On Fri, Sep 17, 2004 at 12:55:40PM EST, Mark
Knecht wrote:
Hi,
I'm trying to follow Dave's instructions for building fst-1.6
http://www.djcj.org/LAU/quicktoots/toots/vst-plugins/
at the section called "Building and Installing the fst System" on my
Gentoo laptop. Here's wht I'm doing:
<Snip>
flash fst-1.6 $ make
<SNIP>
gcc -c -I. -Iinclude -I/usr/include/wine/windows/..
-I/usr/include/wine/windows/../.. -I/usr/include/wine/windows -g -O2
-fPIC -I .. -I./vst -DDLLPATH=\"/usr/lib/wine\"
-DLIBPATH=\"/usr/local/lib\" -D_REENTRANT -o fstconfig.o fstconfig.c
gcc -o fstconfig fstconfig.o -L. -lfst make[1]: Leaving directory
`/home/mark/data/VST/fst-1.6/fst'
flash fst-1.6 $ su -
Password: root@flash ~ # cd ~mark/data/VST/fst-1.6
root@flash /home/mark/data/VST/fst-1.6 # make install
/bin/sh ./mkinstalldirs /usr/local/lib/pkgconfig
./mkinstalldirs: ./mkinstalldirs: No such file or directory
make: *** [install-pkgconfigDATA] Error 127
root@flash /home/mark/data/VST/fst-1.6 #
The mkinstalldirs file in the tarball is missing. Either grab this
file from
another file, or search through your autoconf files for a copy of this
file.
found in /usr/share/automake-ver where ver is the version of automake you
have installed.
There is the one mistake in the instructions on
the QuickToot page where
it seems to tell me to run fixheaders from the wrong place, but I
haven't figured out how to get past this.
You need to get the vst header files, and put them in the vst
subdirectory
of the tarball. Then from the vst directory, run ../fixheaders.
However, there
is more you have to do to the headers. I am not at my audio box right
now, and
can't remember off the top of my head.