And if possible, selective runtime debugging per sub-system. This would make developing and debugging parts of Amarok easier.<br><br><div><span class="gmail_quote">2007/8/3, Nikolaj Hald Nielsen <<a href="mailto:nhnfreespirit@gmail.com">
nhnfreespirit@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I think it would be really useful.<br><br>I am all for the "give it a try and see how it goes" approach as
<br>opposed to thinking too much about it and never doing anything! :-)<br><br><br><br>On 8/3/07, Mark Kretschmann <<a href="mailto:kretschmann@kde.org">kretschmann@kde.org</a>> wrote:<br>> This happened today on #amarok:
<br>><br>> 09:24 < Kebianizao> markey: is there a verbose option for amarokapp?<br>> 09:25 < markey> --enable-debug=full<br>> 09:25 < markey> compile time<br>> 09:25 < Kebianizao> do you really have to rebuild to get that?
<br>> 09:25 < Kebianizao> :O<br>><br>> Which makes me wonder (again) if we shouldn't make our debug output a<br>> runtime option, e.g. "amarok --debug". We've discussed this briefly<br>
> some time ago, but no decision was reached.<br>><br>> I think the advantages of this approach are obvious (no rebuilding<br>> needed), so I'm wondering about the disadvantages. It might make the<br>> binary somewhat bigger, but that's all I can think of.
<br>><br>> --<br>> Mark<br>> _______________________________________________<br>> Amarok-devel mailing list<br>> <a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br>> <a href="https://mail.kde.org/mailman/listinfo/amarok-devel">
https://mail.kde.org/mailman/listinfo/amarok-devel</a><br>><br>_______________________________________________<br>Amarok-devel mailing list<br><a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/amarok-devel">
https://mail.kde.org/mailman/listinfo/amarok-devel</a><br></blockquote></div><br>