From: Jim Peters (jim_at_uazu.net)
Date: 2002-02-27 15:49:07
Doug Sutherland wrote:
> I'm going to try doing a full build on windows next, I expect that
> to be painful :O)
A build of BWView on Windows ? Ouch! Let me tell you my 'hacks'
(using MinGW/MSYS): The build of FFTW failed for me in 'make' trying
to put the .a files together, so I just linked with all the FFTW .o
files manually. Maybe the problem is soluable, but I just wanted to
get it working. I think I also had to move all the bits around for
SDL too.
In addition, to get console output working, you need to add this code
after the main() routine in bwview.c:
#ifdef main
#undef main
extern int console_main(int,char**);
int main(int ac, char **av) { return console_main(ac, av); }
#endif
That's because with SDL on Win32, 'main' is normally #defined to
SDL_main so that SDL can do its startup. For some reason, however,
the compiler calls window_main() if a main() isn't present, when in
fact we want it to call console_main(). This is what this little
main() routine does for us. Well, it worked for me, anyway. Again,
there may be a more 'official' solution.
> 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?
With FFTW, you can give ./configure an additional option to put
different prefixes on the front of 32-bit and 64-bit versions, and I
think that is the best option. However, I haven't tried that yet.
I wasn't thinking of putting any SDL code in there at all. There is
no advantage to that as I can see. SDL by itself just gives you a
frame buffer for video, plus all the event framework for input events
and so on, plus some thread stuff and a few other bits and bobs. I
quite liked working at this low level, because when you're talking to
pixels, you know where you are.
For higher-level graphics, there are various libraries. See the SDL
web-site. I looked at some of the graphics primitives stuff, but
decided it would be quicker to write pixels. I haven't looked at GUI
widgets yet at all. That's not really my scene ... ;-(
> 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.
Great -- if you can figure out 'automake', that would be really
useful.
> 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 ...
You could have it say nice things to you if it notices you are getting
stressed. Or it could say deep and meaningful things if it notices
you have reached another plane.
(This isn't a joke, by the way, because I've got a few things I've
recorded myself to lead me through 'mediations' and so on, and I'm
also thinking of having my laptop come out with things randomly
through the day. It's amazing how we respond to repetition, both
positive and negative.)
Jim
-- Jim Peters (_)/=\~/_(_) jim_at_uazu.net (_) /=\ ~/_ (_) Uazú (_) /=\ ~/_ (_) http:// B'ham, UK (_) ____ /=\ ____ ~/_ ____ (_) uazu.net
This archive was generated by hypermail 2.1.4 : 2002-07-27 12:28:39 BST