<div class="gmail_quote">On Mon, Feb 18, 2013 at 7:29 AM, Ralf Habacker <span dir="ltr"><<a href="mailto:ralf.habacker@gmail.com" target="_blank">ralf.habacker@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes, I'm porting code away from kde_file.h (which is the API interface to<br><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
kdewin), when moving it into frameworks.<br>
<br>
What about stuff like mode_t, though? People reported that karchive-qt4 doesn't<br>
build on Windows because of that. Does that come from kdewin too?<br>
</blockquote></div>
in case of visual studio compilers yes. Because they do not define mode_t, a replacement definition is there at <a href="https://projects.kde.org/projects/kdesupport/kdewin/repository/revisions/master/entry/include/msvc/sys/types.h#L70" target="_blank">https://projects.kde.org/projects/kdesupport/kdewin/repository/revisions/master/entry/include/msvc/sys/types.h#L70</a></blockquote>
<div><br>Perhaps it is better to port away from Posix altogether to a more cross-platform solution as Windows is not Posix compliant?<br><br>Once that is done, one could see how much left that is worth the effort of upstreaming.<br>
<br>Laszlo<br><br>PS.: If it is that desperate, perhaps one could work on a QtWinPosix compatibility library upstream. :-)<br></div></div>