The problem with windows stuff, is to have time to do it...
Tipically, this job is delegate to KDE Windows team. This is why this
project exist. They have time, ressource, and guy to do it.
Personnally, i'm the author (With Julien Narboux) of stand alone
version for windows (outdated now). I build it on my computer to learn
NSIS windows installer. I have no plan to maintain it as well.
My prefered devel env. still Linux so far. Windows hack is poor
compared to linux. But i maintain my laptop with digiKam for windows
source code to check if all compile fine under Win7 + Visual C++.
So, what's can be do ? Find somewhere in KDE win team or a windows
user motivated to setup a devel. env and compile/packaging digiKam as
well.
It's not too difficult to do (outside test and hack of course) but it
take a while. And time is precious...
Also, remember that a lots of bug under digiKam for windows come from
KDELIbs, not digiKam source code...
Best
Gilles Caulier
2011/5/20 Paul Verizzo <
[hidden email]>:
> 1. Is there any intention of making the Windows executable for 2.0? I
> know that 1.7 had its flaws, but it was SO nice to not have to get
> digiKam via the KDE Windows folks.
>
> Which leads to 2, has that ever been updated? The problem with that
> route was lack of updates and huge unwanted files and programs to go
> with the KDE, nothing to do with digiKam.
>
> And yes, I have spent untold (wasted) hours trying to run digiKam in a
> Virtual Box, and no, I"m not going the dual boot route; I want full use
> of my computer and programs while using digiKam.
>
> Thanks for all!
>
> Paul
> _______________________________________________
> Digikam-users mailing list
>
[hidden email]
>
https://mail.kde.org/mailman/listinfo/digikam-users>
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users
Locked
