Qtopia-interest Archive, July 2007
Running Qtopia applications
Message 1 in thread
Hi,
I am studying software development and I am looking at Qtopia for developing
applications for linux devices. The device I have at the moment for testing
is a nokia N800. Can I run Qtopia applications on an N800? What do I have
to install on the N800 in order to get applications written in Qtopia to
run. there is an option in configure which states static as opposed to
shared. If I choose this option does it mean that I can just have the
application with nothing else installed.
I have recently installed scratchbox and the maemo sdk into it. Using the
armel environment within scratchbox I tried to configure install qtopia with
the command "./configure -embedded arm -qvfb -depths 4,8,16,32 -xplatform
qws/linux-arm-g++ -armfpa -little-endian -tablet"
it proceeds normally for a couple of seconds and then:
g++ -o "/home/L/qtopia-4.3.0/bin/qmake" project.o property.o main.o
makefile.o unixmake2.o unixmake.o mingw_make.o option.o winmakefile.o
projectgenerator.o meta.o makefiledeps.o metamakefile.o
xmloutput.opbuilder_pbx.o borland_bmake.o msvc_dsp.o msvc_vcproj.o
msvc_nmake.o
msvc_objectmodel.o qstring.o qtextstream.o qiodevice.o qglobal.o
qbytearray.o qbytearraymatcher.o qdatastream.o qbuffer.o qlistdata.o
qfile.oqfsfileengine_unix.o qfsfileengine_iterator_unix.o
qfsfileengine.o qfsfileengine_iterator.o qregexp.o qvector.o qbitarray.o
qdir.o qdiriterator.o quuid.o qhash.o qfileinfo.o qdatetime.o qstringlist.o
qabstractfileengine.o qtemporaryfile.o qmap.o qmetatype.o qsettings.o
qlibraryinfo.o qvariant.o qvsnprintf.o qlocale.o qlinkedlist.o qurl.o
qnumeric.o qcryptographichash.o qscriptasm.o qscriptast.o
qscriptastvisitor.o qscriptcompiler.o qscriptecmaarray.o
qscriptecmaboolean.o qscriptecmacore.o qscriptecmadate.o
qscriptecmafunction.o qscriptecmaglobal.o qscriptecmamath.o
qscriptecmanumber.o qscriptecmaobject.o qscriptecmaregexp.o
qscriptecmastring.o qscriptecmaerror.o qscriptcontext_p.o
qscriptengine.oqscriptengine_p.o
qscriptextenumeration.o qscriptextvariant.o qscriptcontext.o
qscriptfunction.o qscriptgrammar.o qscriptlexer.o qscriptclassdata.o
qscriptparser.o qscriptprettypretty.o qscriptsyntaxchecker.o qscriptvalue.o
qscriptvalueimpl.o qscriptvalueiterator.o
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
terminate called after throwing an instance of 'std::bad_alloc'
...
It gives this same terminate statement about 100 times then
Building on: qws/linux-generic-g++
Building for: qws/linux-arm-g++
Architecture: arm
Build ............... libs examples demos
Configuration ....... cross_compile release shared dll embedded
separate_debug_info qt3support accessibility minimal-config small-config
medium-config large-config full-config embedded png freetype zlib release
Debug ............... no
Qt 3 compatibility .. yes
...
It appears to continue.
When it reaches the section:
Creating makefiles. Please wait...
if throws the same error again for a number of the .pro files that it is
creating
After this a make obviously fails.
Any help will be greatly appreciated.
L
Message 2 in thread
Here are a couple of resources that might help..
http://trolltech.com/products/qtopia/qtopia_core/requirements
http://www.kevinboone.com/myfirstqtopiaapp1.html
Your particular error seems to be due to memory allocation issues. Refer
to
http://www.qtcentre.org/forum/f-qt-programming-2/t-how-big-is-big-for-a-qtable-2-m-rows-is-to-big--5386.html
chris burke
phone: 617-621-0060 x195
email: cburke@xxxxxxx
skype: chris.burke0
Qt learner wrote:
> Hi,
>
> I am studying software development and I am looking at Qtopia for
> developing applications for linux devices. The device I have at the
> moment for testing is a nokia N800. Can I run Qtopia applications on
> an N800? What do I have to install on the N800 in order to get
> applications written in Qtopia to run. there is an option in
> configure which states static as opposed to shared. If I choose this
> option does it mean that I can just have the application with nothing
> else installed.
>
> I have recently installed scratchbox and the maemo sdk into it. Using
> the armel environment within scratchbox I tried to configure install
> qtopia with the command "./configure -embedded arm -qvfb -depths
> 4,8,16,32 -xplatform qws/linux-arm-g++ -armfpa -little-endian -tablet"
>
>
> it proceeds normally for a couple of seconds and then:
>
> g++ -o "/home/L/qtopia-4.3.0/bin/qmake" project.o property.o main.o
> makefile.o unixmake2.o unixmake.o mingw_make.o option.o winmakefile.o
> projectgenerator.o meta.o makefiledeps.o metamakefile.o xmloutput.o
> pbuilder_pbx.o borland_bmake.o msvc_dsp.o msvc_vcproj.o msvc_nmake.o
> msvc_objectmodel.o qstring.o qtextstream.o qiodevice.o qglobal.o
> qbytearray.o qbytearraymatcher.o qdatastream.o qbuffer.o qlistdata.o
> qfile.o qfsfileengine_unix.o qfsfileengine_iterator_unix.o
> qfsfileengine.o qfsfileengine_iterator.o qregexp.o qvector.o
> qbitarray.o qdir.o qdiriterator.o quuid.o qhash.o qfileinfo.o
> qdatetime.o qstringlist.o qabstractfileengine.o qtemporaryfile.o
> qmap.o qmetatype.o qsettings.o qlibraryinfo.o qvariant.o qvsnprintf.o
> qlocale.o qlinkedlist.o qurl.o qnumeric.o qcryptographichash.o
> qscriptasm.o qscriptast.o qscriptastvisitor.o qscriptcompiler.o
> qscriptecmaarray.o qscriptecmaboolean.o qscriptecmacore.o
> qscriptecmadate.o qscriptecmafunction.o qscriptecmaglobal.o
> qscriptecmamath.o qscriptecmanumber.o qscriptecmaobject.o
> qscriptecmaregexp.o qscriptecmastring.o qscriptecmaerror.o
> qscriptcontext_p.o qscriptengine.o qscriptengine_p.o
> qscriptextenumeration.o qscriptextvariant.o qscriptcontext.o
> qscriptfunction.o qscriptgrammar.o qscriptlexer.o qscriptclassdata.o
> qscriptparser.o qscriptprettypretty.o qscriptsyntaxchecker.o
> qscriptvalue.o qscriptvalueimpl.o qscriptvalueiterator.o
> terminate called after throwing an instance of 'std::bad_alloc'
> what(): St9bad_alloc
> terminate called after throwing an instance of 'std::bad_alloc'
> what(): St9bad_alloc
> terminate called after throwing an instance of 'std::bad_alloc'
> what(): St9bad_alloc
> terminate called after throwing an instance of 'std::bad_alloc'
> what(): St9bad_alloc
> terminate called after throwing an instance of 'std::bad_alloc'
> ...
>
> It gives this same terminate statement about 100 times then
>
> Building on: qws/linux-generic-g++
> Building for: qws/linux-arm-g++
> Architecture: arm
>
> Build ............... libs examples demos
> Configuration ....... cross_compile release shared dll embedded
> separate_debug_info qt3support accessibility minimal-config
> small-config medium-config large-config full-config embedded png
> freetype zlib release
> Debug ............... no
> Qt 3 compatibility .. yes
> ...
>
> It appears to continue.
>
> When it reaches the section:
> Creating makefiles. Please wait...
> if throws the same error again for a number of the .pro files that it
> is creating
>
> After this a make obviously fails.
>
>
> Any help will be greatly appreciated.
> L
>
>
--
[ signature omitted ]
Message 3 in thread
Chris,
Thank you for your feedback it has been extremely helpful. Just for
clarity: if I configure Qtopia with the -singleexec option does this mean
that I do not have to have Qtopia installed on the target device. the
application will be standalone?
secondly I followed the thread in www.qtcentre.org. It suggested checking
ulimit -a.
On my standard system:
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 20
file size (blocks, -f) unlimited
pending signals (-i) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) unlimited
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
and within the scratchbox:
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) unlimited
virtual memory (kbytes, -v) unlimited
as you can see the only common variables that are not unlimited are:
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) 8192
yet I have had no problems installing Qtopia into my main system, outside
the scratchbox.
Do you have any ideas as to what the problem with the memory allocation
might be?
Thanks in advance
On 7/2/07, Chris Burke <cburke@xxxxxxx> wrote:
>
> Here are a couple of resources that might help..
>
> http://trolltech.com/products/qtopia/qtopia_core/requirements
> http://www.kevinboone.com/myfirstqtopiaapp1.html
>
> Your particular error seems to be due to memory allocation issues. Refer
> to
>
> http://www.qtcentre.org/forum/f-qt-programming-2/t-how-big-is-big-for-a-qtable-2-m-rows-is-to-big--5386.html
>
> chris burke
> phone: 617-621-0060 x195
> email: cburke@xxxxxxx
> skype: chris.burke0
>
>
>
> Qt learner wrote:
> > Hi,
> >
> > I am studying software development and I am looking at Qtopia for
> > developing applications for linux devices. The device I have at the
> > moment for testing is a nokia N800. Can I run Qtopia applications on
> > an N800? What do I have to install on the N800 in order to get
> > applications written in Qtopia to run. there is an option in
> > configure which states static as opposed to shared. If I choose this
> > option does it mean that I can just have the application with nothing
> > else installed.
> >
> > I have recently installed scratchbox and the maemo sdk into it. Using
> > the armel environment within scratchbox I tried to configure install
> > qtopia with the command "./configure -embedded arm -qvfb -depths
> > 4,8,16,32 -xplatform qws/linux-arm-g++ -armfpa -little-endian -tablet"
> >
> >
> > it proceeds normally for a couple of seconds and then:
> >
> > g++ -o "/home/L/qtopia-4.3.0/bin/qmake" project.o property.o main.o
> > makefile.o unixmake2.o unixmake.o mingw_make.o option.o winmakefile.o
> > projectgenerator.o meta.o makefiledeps.o metamakefile.o xmloutput.o
> > pbuilder_pbx.o borland_bmake.o msvc_dsp.o msvc_vcproj.o msvc_nmake.o
> > msvc_objectmodel.o qstring.o qtextstream.o qiodevice.o qglobal.o
> > qbytearray.o qbytearraymatcher.o qdatastream.o qbuffer.o qlistdata.o
> > qfile.o qfsfileengine_unix.o qfsfileengine_iterator_unix.o
> > qfsfileengine.o qfsfileengine_iterator.o qregexp.o qvector.o
> > qbitarray.o qdir.o qdiriterator.o quuid.o qhash.o qfileinfo.o
> > qdatetime.o qstringlist.o qabstractfileengine.o qtemporaryfile.o
> > qmap.o qmetatype.o qsettings.o qlibraryinfo.o qvariant.o qvsnprintf.o
> > qlocale.o qlinkedlist.o qurl.o qnumeric.o qcryptographichash.o
> > qscriptasm.o qscriptast.o qscriptastvisitor.o qscriptcompiler.o
> > qscriptecmaarray.o qscriptecmaboolean.o qscriptecmacore.o
> > qscriptecmadate.o qscriptecmafunction.o qscriptecmaglobal.o
> > qscriptecmamath.o qscriptecmanumber.o qscriptecmaobject.o
> > qscriptecmaregexp.o qscriptecmastring.o qscriptecmaerror.o
> > qscriptcontext_p.o qscriptengine.o qscriptengine_p.o
> > qscriptextenumeration.o qscriptextvariant.o qscriptcontext.o
> > qscriptfunction.o qscriptgrammar.o qscriptlexer.o qscriptclassdata.o
> > qscriptparser.o qscriptprettypretty.o qscriptsyntaxchecker.o
> > qscriptvalue.o qscriptvalueimpl.o qscriptvalueiterator.o
> > terminate called after throwing an instance of 'std::bad_alloc'
> > what(): St9bad_alloc
> > terminate called after throwing an instance of 'std::bad_alloc'
> > what(): St9bad_alloc
> > terminate called after throwing an instance of 'std::bad_alloc'
> > what(): St9bad_alloc
> > terminate called after throwing an instance of 'std::bad_alloc'
> > what(): St9bad_alloc
> > terminate called after throwing an instance of 'std::bad_alloc'
> > ...
> >
> > It gives this same terminate statement about 100 times then
> >
> > Building on: qws/linux-generic-g++
> > Building for: qws/linux-arm-g++
> > Architecture: arm
> >
> > Build ............... libs examples demos
> > Configuration ....... cross_compile release shared dll embedded
> > separate_debug_info qt3support accessibility minimal-config
> > small-config medium-config large-config full-config embedded png
> > freetype zlib release
> > Debug ............... no
> > Qt 3 compatibility .. yes
> > ...
> >
> > It appears to continue.
> >
> > When it reaches the section:
> > Creating makefiles. Please wait...
> > if throws the same error again for a number of the .pro files that it
> > is creating
> >
> > After this a make obviously fails.
> >
> >
> > Any help will be greatly appreciated.
> > L
> >
> >
>
> --
> To unsubscribe - send "unsubscribe" in the subject to
> qtopia-interest-request@xxxxxxxxxxxxx
>
>
Message 4 in thread
Qt learner wrote:
> Chris,
>
> Thank you for your feedback it has been extremely helpful. Just for
> clarity: if I configure Qtopia with the -singleexec option does this
> mean that I do not have to have Qtopia installed on the target
> device. the application will be standalone?
Yes. From Qtopia 4.2.2 documentation:
/single-exec/ compile - qpe and all the applications are linked together
in a single large binary, however applications are run as separate
processes.
>
> secondly I followed the thread in www.qtcentre.org
> <http://www.qtcentre.org>. It suggested checking ulimit -a.
>
> On my standard system:
>
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 20
> file size (blocks, -f) unlimited
> pending signals (-i) unlimited
> max locked memory (kbytes, -l) unlimited
> max memory size (kbytes, -m) unlimited
> open files (-n) 1024
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) unlimited
> real-time priority (-r) 0
> stack size (kbytes, -s) 8192
> cpu time (seconds, -t) unlimited
> max user processes (-u) unlimited
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
>
> and within the scratchbox:
> core file size (blocks, -c) unlimited
> data seg size (kbytes, -d) unlimited
> file size (blocks, -f) unlimited
> max locked memory (kbytes, -l) unlimited
> max memory size (kbytes, -m) unlimited
> open files (-n) 1024
> pipe size (512 bytes, -p) 8
> stack size (kbytes, -s) 8192
> cpu time (seconds, -t) unlimited
> max user processes (-u) unlimited
> virtual memory (kbytes, -v) unlimited
>
>
> as you can see the only common variables that are not unlimited are:
>
> open files (-n) 1024
> pipe size (512 bytes, -p) 8
> stack size (kbytes, -s) 8192
>
> yet I have had no problems installing Qtopia into my main system,
> outside the scratchbox.
>
> Do you have any ideas as to what the problem with the memory
> allocation might be?
>
> Thanks in advance
I haven't run into the problem myself and haven't been able to find too
much on it besides the memory issues. Look around for tutorials or
someone who has built Qtopia for the 770 or 800.
>
>
> On 7/2/07, *Chris Burke* <cburke@xxxxxxx <mailto:cburke@xxxxxxx>> wrote:
>
> Here are a couple of resources that might help..
>
> http://trolltech.com/products/qtopia/qtopia_core/requirements
> http://www.kevinboone.com/myfirstqtopiaapp1.html
>
> Your particular error seems to be due to memory allocation issues.
> Refer
> to
> http://www.qtcentre.org/forum/f-qt-programming-2/t-how-big-is-big-for-a-qtable-2-m-rows-is-to-big--5386.html
>
> chris burke
> phone: 617-621-0060 x195
> email: cburke@xxxxxxx <mailto:cburke@xxxxxxx>
> skype: chris.burke0
>
>
>
> Qt learner wrote:
> > Hi,
> >
> > I am studying software development and I am looking at Qtopia for
> > developing applications for linux devices. The device I have at
> the
> > moment for testing is a nokia N800. Can I run Qtopia
> applications on
> > an N800? What do I have to install on the N800 in order to get
> > applications written in Qtopia to run. there is an option in
> > configure which states static as opposed to shared. If I choose
> this
> > option does it mean that I can just have the application with
> nothing
> > else installed.
> >
> > I have recently installed scratchbox and the maemo sdk into
> it. Using
> > the armel environment within scratchbox I tried to configure install
> > qtopia with the command "./configure -embedded arm -qvfb -depths
> > 4,8,16,32 -xplatform qws/linux-arm-g++ -armfpa -little-endian
> -tablet"
> >
> >
> > it proceeds normally for a couple of seconds and then:
> >
> > g++ -o "/home/L/qtopia-4.3.0/bin/qmake" project.o property.o main.o
> > makefile.o unixmake2.o unixmake.o mingw_make.o option.o
> winmakefile.o
> > projectgenerator.o meta.o makefiledeps.o metamakefile.o xmloutput.o
> > pbuilder_pbx.o borland_bmake.o msvc_dsp.o msvc_vcproj.o msvc_nmake.o
> > msvc_objectmodel.o qstring.o qtextstream.o qiodevice.o qglobal.o
> > qbytearray.o qbytearraymatcher.o qdatastream.o qbuffer.o qlistdata.o
> > qfile.o qfsfileengine_unix.o qfsfileengine_iterator_unix.o
> > qfsfileengine.o qfsfileengine_iterator.o qregexp.o qvector.o
> > qbitarray.o qdir.o qdiriterator.o quuid.o qhash.o qfileinfo.o
> > qdatetime.o qstringlist.o qabstractfileengine.o qtemporaryfile.o
> > qmap.o qmetatype.o qsettings.o qlibraryinfo.o qvariant.o
> qvsnprintf.o
> > qlocale.o qlinkedlist.o qurl.o qnumeric.o qcryptographichash.o
> > qscriptasm.o qscriptast.o qscriptastvisitor.o qscriptcompiler.o
> > qscriptecmaarray.o qscriptecmaboolean.o qscriptecmacore.o
> > qscriptecmadate.o qscriptecmafunction.o qscriptecmaglobal.o
> > qscriptecmamath.o qscriptecmanumber.o qscriptecmaobject.o
> > qscriptecmaregexp.o qscriptecmastring.o qscriptecmaerror.o
> > qscriptcontext_p.o qscriptengine.o qscriptengine_p.o
> > qscriptextenumeration.o qscriptextvariant.o qscriptcontext.o
> > qscriptfunction.o qscriptgrammar.o qscriptlexer.o qscriptclassdata.o
> > qscriptparser.o qscriptprettypretty.o qscriptsyntaxchecker.o
> > qscriptvalue.o qscriptvalueimpl.o qscriptvalueiterator.o
> > terminate called after throwing an instance of 'std::bad_alloc'
> > what(): St9bad_alloc
> > terminate called after throwing an instance of 'std::bad_alloc'
> > what(): St9bad_alloc
> > terminate called after throwing an instance of 'std::bad_alloc'
> > what(): St9bad_alloc
> > terminate called after throwing an instance of 'std::bad_alloc'
> > what(): St9bad_alloc
> > terminate called after throwing an instance of 'std::bad_alloc'
> > ...
> >
> > It gives this same terminate statement about 100 times then
> >
> > Building on: qws/linux-generic-g++
> > Building for: qws/linux-arm-g++
> > Architecture: arm
> >
> > Build ............... libs examples demos
> > Configuration ....... cross_compile release shared dll embedded
> > separate_debug_info qt3support accessibility minimal-config
> > small-config medium-config large-config full-config embedded png
> > freetype zlib release
> > Debug ............... no
> > Qt 3 compatibility .. yes
> > ...
> >
> > It appears to continue.
> >
> > When it reaches the section:
> > Creating makefiles. Please wait...
> > if throws the same error again for a number of the .pro files
> that it
> > is creating
> >
> > After this a make obviously fails.
> >
> >
> > Any help will be greatly appreciated.
> > L
> >
> >
>
> --
> To unsubscribe - send "unsubscribe" in the subject to
> qtopia-interest-request@xxxxxxxxxxxxx
> <mailto:qtopia-interest-request@xxxxxxxxxxxxx>
>
>
chris burke
phone: 617-621-0060 x195
email: cburke@xxxxxxx
skype: chris.burke0
--
[ signature omitted ]
Message 5 in thread
On Tuesday 03 July 2007 22:41, Qt learner wrote:
> Chris,
>
> Thank you for your feedback it has been extremely helpful. Just for
> clarity: if I configure Qtopia with the -singleexec option does this mean
> that I do not have to have Qtopia installed on the target device. the
> application will be standalone?
No, it doesn't. -singleexec is used in instances where the target device is
not likely to have additional applications installed later and space is a
premium, for example a voip handset. Because there are no dynaically linked
libraries you can't install applications later that would need to link to the
libraries as well, however the compiler can optimize better for size and
generally there is a performance improvement as well.
Currently there is no supported way to write Qtopia applications for
non-Qtopia devices. It is possible to write a stand-alone Qtopia application
because that is all the qpe binary in the Qtopia platform is.
http://doc.trolltech.com/qtopia4.2/qtopiaapplication.html#QtopiaApplication
However this is more akin to writing an alternative Qtopia installation rather
than a stand-alone Qtopia application. By this I mean if there is already
some server or mechanism allowing applications to access the frame buffer and
key/touchscreen input, you can either replace it with a Qtopia GuiServer
instance, or you can work with it with a Qtopia GuiClient instance if it
already is a Qtopia GuiServer.
However in the specific instance of the Nokia N800, I believe it is running an
X11 server. In this case your best bet is to use Qt/X11.
--
[ signature omitted ]
