Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
Icu header files missing
-
In my QT 5.1 source, there is no file udat.h.
The file /qt-everywhere-opensource-src-5.1.0/qtwebkit/Source/JavaScriptCore/runtime/DatePrototype.cpp includes it.
I'm happy to change the include path to point to it, but I can't seem to locate it...
Where is udat.h?
-
Hi and welcome to devnet,
ICU is a dependency you have to install before compiling Qt.
Otherwise if you don't use WebKit you can also avoid building it
-
Hi, thanks.
Ok, but there's an icu folder in that directory. Shouldn't it have what I need? I modified the makefiles for several of the other folders to include ./icu/, and that seems to of gotten them over the hump.
-
If I'm not mistaken, this folder contains only headers so nothing to link against
-
Ah, right. I do have libicu-dev installed, but hadn't thought to point QT to my system /usr/include directory. I'll add it to the end of the list. Thanks.
-
On another note, if these files are required in the system, shouldn't QT look there by default?
-
ICU is not required, unless you want to build QtWebKit
-
Ok, but in the make files for QtWebKit, it should point to the systems /usr/include directory, no?
-
I haven't checked recently but I'm not sure that ICU is installed by default on linux
-
That's not really the issue here. Even if I do have them installed, the make file will never find them, unless I go and edit it. It's not a good idea to make people edit make files in order to install the framework. If it is installed, it will probably be in /usr/include. The make files should point there by default.
-
Are you sure you have ICU's headers installed ? Installing the library doesn't mean that the headers are also there. Generally they are part of the corresponding dev-package
-
I'm sure. As I mentioned earlier, libicu-dev is installed.
-
I think you're still missing the point. How in the world does the make file know if I have ICU installed or not? It doesn't even try to look into /usr/include.
-
The makefile doesn't. It's the configure scripts that searches for installed elements to do the automatic enabling/disabling of features.
-
Well, really the configure script uses my qconf file to tell the make files where to look. But yes, it happens when you execute the configuration. I will add /usr/include.
