Content-Type: text/plain; charset=ISO-8859-1
A) If you just test with a single input file, you get a uniform debugging
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).
On Thu, Dec 22, 2011 at 9:55 AM, firstname.lastname@example.org
> Hi everyone. I'm starting to write a simple filter and I want to expose it
Content-Type: text/html; charset=ISO-8859-1
A) If you just test with a single input file, you get a uniform debuggi=
ng environment.B) You can set breakpoints and debug inside your LV2 plu=
gin just like you would any other C library code (so long as you compiled i=
n debugging information to the shared library).
Hi everyone. I'm starting to write a sim=
ple filter and I want to expose it as an lv2 plugin.=A0=
My development environment is very simple right now: vim editor, gcc compil=
er, 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.=A0
I've found this setup to be a bit unconfortable bec=
ause once I load the plugin in ardour I don't know how to get debug inf=
ormation from it (print statements or breakpoints with gdb).
What does a lv2 development environment typically looks like=
? what are you guys using?Thanks!
-- Rafael Vegaemail.email@example.com
Linux-audio-dev mailing list