Bring kdewin back?

[Kevin Ottens]

Hello,

On Monday 14 October 2013 18:42:02 Nicolás Alvarez wrote:
> While trying to get KDE Frameworks to build on Windows, I found the
> codebase of KDirWatch is full of Unixisms. I did a few improvements
> towards getting it to build on Windows, but I'm now getting several
> errors related to the lack of symbolic links (such as no lstat). It's
> clear this code couldn't have possibly worked on Windows directly, and
> the only way it ever worked is through the use of kdewin to provide
> Unix-like compatibility headers.
> 
> Other libraries have similar problems. It seems to me that someone
> removed the dependency on kdewin without making the code actually work
> without it. Why was it removed? Where can I find the discussion about
> it, if there was any?

Yes it has been discussed, I don't have the thread handy. The point was that 
it wasn't really acceptable to have that extra-dependency in the tier scheme. 
We've been working on removing as many unixisms as possible, apparently not 
enough but we didn't get many people looking at how it was building on 
windows. I'm glad someone finally does.

> If the intention is getting rid of the kdewin dependency, can we
> *temporarily* bring it back to get things to work again, and then remove it
> *progressively* as things get fixed?

If that makes your job easier, I don't see any problem at reintroducing it 
temporarily and fix it progressively. It needs someone to actively monitor the 
progress in that direction though, I'm not well equipped to do that ATM.

Regards.
-- 
Kévin Ottens, http://ervin.ipsquad.net

Sponsored by KDAB to work on KDE Frameworks
KDAB - proud supporter of KDE, http://www.kdab.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20131015/46bac981/attachment.sig>