[Clam-devel] Developing with Network Editor

[Xavier Amatriain]

(And my last for the day ;)

I have been doing some debugging using Network Editor these past days.
Actually I have been using it in what should be one of its main
settings: developing new processing classes. A few things have slowed
down my development beyond what would be expected. Many of them deal
with some build system issues already commented but I thought worthwhile
listing them:

- Library paths and multiple locations. Finding out what library
NetworkEditor is liking against and which one is loading at run-time can
be pretty challenging.
- Multiple headers. After I solved the previous issue I realized that I
could not debug anything in the /CLAM source tree without running the
risk of losing my head. Having headers copied in three different
locations is pretty insane when developing/debugging. Taking whatever
you are developing outside of the main CLAM tree (and into
NetworkEditor/processing for instance) should be the default recommended
instructions.
- Audio I/O weirdness. I still don't understand why Jack does work with
some settings and not others or why I have to restart it every now and
then. Having to use the Jack layer has not helped for developing
(although it is an incredible feature otherwise) but I have not managed
to get PortAudio to work, should it be working fine in Linux now?

(I must say that, apart from that, other inconveniences came from the
fact that, as I mentioned, I have been trying out Eclipse with Scons. In
that respect, I am now convinced that this is worth it)


-- 
/*********************************
 *       Xavier Amatriain        *
 *  Associate Director - MATi    *
 *  Research Director - CREATE   *
 *    UCSB, Santa Barbara CA     *
 *      1-(805)- 893 83 52       *
 ********************************/