I guess you'll need to distribute all the dependencies (dlls) plus dbus. That's what simon (<a href="http://www.simon-listens.org">www.simon-listens.org</a>) installer does. I guess there should be some way to make packages which KDE-Installer understands (so it can resolve the dependencies) - maybe Amarok mirror is an example of that.<br>
<br><div class="gmail_quote">2010/10/31 velociraptor Genjix <span dir="ltr"><<a href="mailto:aphidia@hotmail.com">aphidia@hotmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Hey,<br>
I'm writing an app ( <a href="http://www.youtube.com/watch?v=8tAASvcrJ78" target="_blank">http://www.youtube.com/watch?v=8tAASvcrJ78</a> ) and would really like to use KDE instead of vanilla Qt. I don't want to use much beyond the theming and a few widgets. Someone mentioned this project, but if I distribute my app for windows then will I also need to bundle the whole KDE desktop? Seems excessive... Is building apps for Windows mature yet? Can you point me to a few KDE apps built on Windows so I can test them out (performance, stability .etc).<br>
Thanks ;)<br>
_______________________________________________<br>
Kde-windows mailing list<br>
<a href="mailto:Kde-windows@kde.org">Kde-windows@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-windows" target="_blank">https://mail.kde.org/mailman/listinfo/kde-windows</a><br>
</blockquote></div><br>