Re: [buildcheapeeg] Question for Jim-P

From: Doug Sutherland (wearable_at_earthlink.net)
Date: 2002-02-27 12:17:46


Hi Jim,

>> It appears that libXv is for XVideo hardware video acceleration.
> I'm sorry you had all these problems whilst I was sleeping

No problem, actually I'm glad I went through that.

> You now know many times more about libXv than I ever did. It
> was just something I had to stick in the link to get it to build.

<g> Many times more isn't much, I had no idea what it was before
today, and there is very little info on that on the web. I still
don't know where it comes from (it's not in slackware), I'm just
glad I don't need it. Apparently, some systems come with only
the libXv.a libray (not shared library), and in those cases you
need to do this trick to create the shared libraries:

ld --whole-archive -shared -o libXv.so.1 libXv.a
ln -s libXv.so.1 libXv.so
ldconfig

Same goes for libxXf86dga if that is missing
ld --whole-archive -shared -o libXxf86dga.so libXxf86dga.a

> You're right -- I should learn about automake and get the build
> process more standard somehow.

Your mk file is fine, but that GNU automake is sweet, every
time I see packages set up that way I smile from ear to ear.
If all linux software was set up that way it would be almost
trivial for anyone to compile from source. The nice thing
about automake is it's distro independent, it will figure
out where everything goes. Installing SDL and FFTW from the
source was totally painless. Manual editing of make files
is a nightmare, not bad in small packages like yours, but
sometimes it takes many hours just to understand the make
files and then figure out your distribution too. I'm going
to try doing a full build on windows next, I expect that
to be painful :O)

> The reason I was thinking of putting a chunk of the FFTW
> code into the source bundle was because of some of the
> build problems on Windows and the fact that we don't
> really need the user to install the FFTW libraries,
> especially if they have the 64-bit version already
> installed.

Hmmm, oh yeah I forgot about the 32-bit aspect. Perhaps
it makes sense for FFTW but I really don't think it's
worth slicing and dicing SDL. By the way, does SDL have
GUI widgets too, or do we need to get those elsewhere?

> There are solutions to this, though, and I think you're
> right -- I should try and give it the standard
> "./configure; make; make install" build process.

Well, maybe I can look into that for you and try setting
it up for your code. I want to get automake working with
my Java stuff too.

> Thanks! -- I saw the pictures. OpenEEG is already
> reaching the places no other EEG software has ever
> reached before!

No actual EEG yet, but having run your code on that purse
I really do want EEG in there, it will be quite a unique
peice of fashion :) It already talks and controls home
appliances. It would be a small leap (programatically) to
control appliances with brain wave thresholds ...

-- Doug



This archive was generated by hypermail 2.1.4 : 2002-07-27 12:28:39 BST