1
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
you need to link to libqpe and possibly libqtopia as well.Maybe, this is the same problem as I had.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=136298\"][{POST_SNAPBACK}][/a][/div]
QuoteThe first problem is fixed.
This was in "glibc" library i.e. it must be installed on Suse for development.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147666\"][{POST_SNAPBACK}][/a][/div]
But now I have linker problems it showed that "QPEAppplication::QPEAppplication()" not found and all members from QWidget.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147667\"][{POST_SNAPBACK}][/a][/div]
The first problem is fixed.
This was in "glibc" library i.e. it must be installed on Suse for development.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147666\"][{POST_SNAPBACK}][/a][/div]
Note that the Qtopia API has been broken up into two seperate libraries. One library is called libqpe and the other library is libqtopia1. libqpe 1.5.2 is binary compatible with the existing libqpe 1.5.0 and libqpe 1.5.1 libraries. libqtopia1 contains the source code for the additional methods and classes added to Qtopia for the Qtopia 1.7.0 release. Qtopia 1.7 applications depend on both of these libraries. Qtopia 1.5 devices will be able to install Qtopia 1.7 applications by installing libqtopia1 and any other libraries they need.
Kdevelop 3.x specifically supports Qtopia projects (Create a new project and look under C++/Embedded/Qtopia Application) which are based on tmake. Note that you have to run it from a terminal after setting up your build environment with something like the script dev-x86-qpe.sh It has even more support for OPIE btw. Also see this tutorial:
http://www.kdevelop.org/3.0/doc/tutorial_qtopia/
(The Kdevelop version is a little out of date but it does work with the Qtopia 1.5 SDK as well as v1.6)
QT Designer v2 comes with the Qtopia SDK and kdevelop can still use its .ui files within a project although you have to explicitely use Designer v2 rather than 3. I just created an extra Tools menu entry for this as double clicking a .ui file in kdevelop opens it in Designer v3.
The one thing that I don't like about kdevelop is the code completion doesn't seem to work properly. I've created a permanent store of the Qtopia include files and ctags of my stuff too, but the context sensitivity just isn't there, nor are function info tooltips. I don't particularly like Micro$oft but my day job is programming in Visual Basic and Visual C++ and the 'IntelliSense' stuff really helps get the job done faster. Has anyone got this to work properly in kdevelop? I only use the SuSE RPMs so they could be broken.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=48488\"][{POST_SNAPBACK}][/a][/div]
The 1.7 sdk can be used to create apps for Sharp rom, provided you remove the -lqtopia from tmake.conf as he has done, and thus would not need to install libqtopia.
Qtopia is backwards compatible.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=51428\"][{POST_SNAPBACK}][/a][/div]
Personally I have had no problems doing development for the Z under SuSE 10.0 . I have been able to cross compile kernels and applications quick and easy using the How-To guides on the user group website. The only thing I have not tried doing is cross compiling Qtopia apps, everything that I have compiled has been console based. But I would recommend giving SuSE a go, it does a lot of other things well besides Z dev too.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=105979\"][{POST_SNAPBACK}][/a][/div]