KMid development
Patrick Spendrin
ps_ml at gmx.de
Tue Apr 6 00:20:29 CEST 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 05.04.2010 23:58, schrieb Pedro Lopez-Cabanillas:
> Hi,
>
> This message is just to tell you that I've started the development of a
> Windows native backend for KMid. There are already working backends for Linux
> and Mac OSX at the repository (extragear/multimedia/kmid).
>
> I've installed a mingw4 build environment in the winxp partition of my laptop,
> after solving a few minor problems, and now I can successfully compile kmid's
> SVN sources (there is a dummy test backend, just to get the UI working). The
> question is: do I need to try also the MS VisualC compiler? I would prefer to
> avoid it. Maybe is it possible to add KMid to the kdewin automated builds to
> get the compiler errors from MSVC?
We could add a package to our emerge build scripts, and later also add
that to our build server. This would also mean that you could build kmid
on both mingw and msvc (which are not that different, so normally you
can build stuff on msvc too with only minor changes).
I will look into it later tonight or tomorrow and add an emerge target
at least.
>
> Regards,
> Pedro
regards,
Patrick
> _______________________________________________
> Kde-windows mailing list
> Kde-windows at kde.org
> https://mail.kde.org/mailman/listinfo/kde-windows
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (MingW32)
iEYEARECAAYFAku6Yi0ACgkQi49rfdk/G3ac+QCfTrPTy/295DWOgfv31AY6zgmN
IugAoKu/G1xp25qRG/p9d1YNCY6rXkJh
=A11Y
-----END PGP SIGNATURE-----
More information about the Kde-windows
mailing list