win32 port and svn
Nikolaj Hald Nielsen
nhnfreespirit at gmail.com
Wed Nov 21 13:37:31 UTC 2007
Last I heard, the current trunk actually built with no major issues on
Windows. The only real issue ( Besides getting Amarok2 usable in the
first place ) is, as you mention, the lack of a n audio backend. The
current consensus among the developers is to wait it out until Qt4.4
is releases which will, to the best of our knowledge, include a
working phonon backend for Widows.
However, you are of course welcome to check the code for build issues,
and if you really want to take on the task of building a working
backend, who's to stop you? :-)
That is just my opinion, does anyone feel otherwise?
- Nikolaj
On Nov 21, 2007 2:26 PM, Shane King <kde at dontletsstart.com> wrote:
> Hi folks,
>
> A while back I did a bit of stuff on amarok, but it sort of dropped down
> my priority list since I do most of my listening at work and a job
> writing windows software meant no amarok for me.
>
> However, with the win32 port of kde starting to look like it almost
> works (read: compiles with some gnashing of teeth and sorta runs), I'm
> interested in getting amarok up and running on windows (as in, I'm
> willing to do the work, not beg for a port).
>
> I realise there's no backend to play audio at the moment, but that's
> fixable (or QT might beat me to it), and besides, at the moment it needs
> a bit of work to even compile anyway.
>
> Which is why I'm writing this: are there any objections to me checking
> in win32 porting fixes to svn? I'll of course make every effort to
> ensure I don't break it for unix builds.
>
> Thought it'd be best to ask here to be sure first rather than upset
> anyone. :)
>
> Shane.
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok
>
More information about the Amarok
mailing list