On Mon, Feb 18, 2013 at 7:29 AM, Ralf Habacker <ralf.habac...@gmail.com>wrote:
> Yes, I'm porting code away from kde_file.h (which is the API interface to > >> kdewin), when moving it into frameworks. >> >> What about stuff like mode_t, though? People reported that karchive-qt4 >> doesn't >> build on Windows because of that. Does that come from kdewin too? >> > in case of visual studio compilers yes. Because they do not define mode_t, > a replacement definition is there at > https://projects.kde.org/projects/kdesupport/kdewin/repository/revisions/master/entry/include/msvc/sys/types.h#L70 Perhaps it is better to port away from Posix altogether to a more cross-platform solution as Windows is not Posix compliant? Once that is done, one could see how much left that is worth the effort of upstreaming. Laszlo PS.: If it is that desperate, perhaps one could work on a QtWinPosix compatibility library upstream. :-)
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
