Jump to content

Frameworks/Windows: Difference between revisions

From KDE Community Wiki
Nalvarez (talk | contribs)
Nalvarez (talk | contribs)
KCoreAddons: Show the KRandom error message too
Line 9: Line 9:
KRandom fails to build due to the use of <code>unistd.h</code> and <code>getpid()</code>. KDirWatch also fails. Several portability fixes were done, but still not enough:
KRandom fails to build due to the use of <code>unistd.h</code> and <code>getpid()</code>. KDirWatch also fails. Several portability fixes were done, but still not enough:
<pre>
<pre>
tier1\kcoreaddons\src\lib\randomness\krandom.cpp(25) : fatal error C1083: Cannot open include file: 'unistd.h': No such file or directory
tier1\kcoreaddons\src\lib\io\kdirwatch.cpp(845) : error C3861: 'QT_LSTAT': identifier not found
tier1\kcoreaddons\src\lib\io\kdirwatch.cpp(845) : error C3861: 'QT_LSTAT': identifier not found
tier1\kcoreaddons\src\lib\io\kdirwatch.cpp(846) : error C2065: 'QT_STAT_LNK': undeclared identifier
tier1\kcoreaddons\src\lib\io\kdirwatch.cpp(846) : error C2065: 'QT_STAT_LNK': undeclared identifier

Revision as of 00:25, 15 October 2013

This page tracks the status of KDE Frameworks on Microsoft Windows.

I have only tested with MSVC2010 32-bit.

Tier 1

Working: itemmodels, itemviews, kplotting, kcodecs, kguiaddons, kidletime, kwidgetsaddons, sonnet. More details later.

KCoreAddons

KRandom fails to build due to the use of unistd.h and getpid(). KDirWatch also fails. Several portability fixes were done, but still not enough:

tier1\kcoreaddons\src\lib\randomness\krandom.cpp(25) : fatal error C1083: Cannot open include file: 'unistd.h': No such file or directory
tier1\kcoreaddons\src\lib\io\kdirwatch.cpp(845) : error C3861: 'QT_LSTAT': identifier not found
tier1\kcoreaddons\src\lib\io\kdirwatch.cpp(846) : error C2065: 'QT_STAT_LNK': undeclared identifier
tier1\kcoreaddons\src\lib\io\kdirwatch.cpp(1294) : error C3861: 'nlink_t': identifier not found

Note that this code would have never worked on Windows directly. It only ever worked thanks to the use of kdewin to provide compatibility headers.

KDirWatch also has some code working around a Windows limitation, which is obsolete because QFileSystemWatcher already implements the same workaround. But I'm not touching that until I get it to build.

KArchive

Not tested yet, due to external dependencies for compression (didn't get around to installing them yet).

KJS

Not tested yet due to PCRE dependency.