Thanks for the links, Jeremy. I assume you use either lv2file or lv2proc within a script to generate output files, is that correct? That sounds powerful to conduct (semi)automated testing.
On Thu, Dec 22, 2011 at 10:55 AM, Jeremy Salwen <[email protected]>wrote: > Hey Rafael, > > I wrote lv2file (https://github.com/jeremysalwen/lv2file) specifically > for debugging lv2 plugins. Also look at lv2proc ( > http://naspro.atheme.org/applications/lv2proc/). > > A) If you just test with a single input file, you get a uniform debugging > environment. > B) You can set breakpoints and debug inside your LV2 plugin just like you > would any other C library code (so long as you compiled in debugging > information to the shared library). > > Jeremy > > On Thu, Dec 22, 2011 at 9:55 AM, [email protected] < > [email protected]> wrote: > >> Hi everyone. I'm starting to write a simple filter and I want to expose >> it as an lv2 plugin. >> >> My development environment is very simple right now: vim editor, gcc >> compiler, package the lv2 manually (will write a script for that in a day >> or two) and then load the plugin in ardour to test it. >> >> I've found this setup to be a bit unconfortable because once I load the >> plugin in ardour I don't know how to get debug information from it (print >> statements or breakpoints with gdb). >> >> What does a lv2 development environment typically looks like? what are >> you guys using? >> >> Thanks! >> >> -- >> Rafael Vega >> [email protected] >> >> _______________________________________________ >> Linux-audio-dev mailing list >> [email protected] >> http://lists.linuxaudio.org/listinfo/linux-audio-dev >> >> > -- Rafael Vega [email protected]
_______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
