Re: Switch to automake *now*?
Ed Sweetman <[email protected]>
| Newsgroups | gmane.comp.audio.zinf.devel |
|---|---|
| Message-ID | <[email protected]> |
Kristian G. Kvilekval wrote: > Andreas, > > I was playing with the new build system and got > the m3u plugin to work. > > I had to concatenate the definitions in config/config.win32 to > config/config.h in order to get m3u.cpp to compile. > > How is the rest of conversion process going? > Should I commit my changes? > > Could you change the default optimization level to -O. > I have a reasonably stable at that level. > > Thanks. Am i the only one who gets the feeling of "oh shit" when simply changing the way we build zinf seriously alters the way it works when compiled? if i have time today (which i think i will) i'm going to go through the plugins, starting at the audio plugins and make a list of all the objects each one touches. When the list is completed, we should have a clear picture of where our problem objects are and we'll be able to definitively decide where locks need to go and where they're not needed at all. I'm pretty sure we all know what the problem is..(signals) but we cant really say for certain where that problem is and why. Hopefully once this mapping of zinf is complete we'll be able to see where and why and fix problem objects that access data directly. I was going to do this anyway for myself in figuring out how to merge my fixes to the pipeline into the cvs head, the build issues just increase the importance of such a mapping. ------------------------------------------------------- This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en