The goal of this test case is to analyze the scenario:
- 1. Develop Harbour project on Linux, targeting a
multiplatform solution (Linux or Windows).
- 2. Test the developed project on Linux.
- 3. Deploy the developed project components on Windows and
Linux.
This scenario is not far away from the corresponding ‘Mingw’ project
under Fedora 11 and above:https://fedoraproject.org/wiki/Features/
Windows_cross_compiler#Summary.
Take as a prerequisite to achieve this scenario a build sequence of
the Harbour components (my thoughts): ’build-harbour-win.sh’.
Errors detected during fine tunings of the components :
1. ‘export HB_WITH_PCRE=no’ or ‘export HB_WITH_PCRE=/usr/i686-
pc-mingw32/sys-root/mingw/include’ generates compiler error
Solution is: ‘export HB_WITH_PCRE=’ or missing.
2. ‘export HB_WITH_ZLIB=/usr/i686-pc-mingw32/sys-root/mingw/
include’ generates compiler error
Solution is: ‘export HB_WITH_ZLIB=local’
3. ‘export HB_WITH_SQLITE3=/usr/i686-pc-mingw32/sys-root/mingw/
include’ sqlite3 is skipped
Solution is: ‘export HB_INC_SQLITE3=local’
4. ‘export HB_WITH_QT=/usr/i686-pc-mingw32/sys-root/mingw/
include’ generates error: no WebKit package.
Solution is: ‘export HB_WITH_QT=no’
This test case was broken by the monolith construction of the hbqt
library, as the Webkit is not yet implemented in mingw port of the
Qt-4.5.2. My proposal is to split it into ‘Gui’, ‘Network’ and
‘Webkit’ with the necessary build detections too.
Please reflect on these, as this decision needs a common thinking.
I agree with splitting hbqt, probably it would be best to create new
subdirs under current hbqt dir for each major qt component (GUI,
Network and WebKit). This would have numerous benefits.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
