Qtopia-interest Archive, January 2008
How to configure qtopia?
Message 1 in thread
Hello
I am trying to configure Qtopia according to the instructions on the
page
http://doc.trolltech.com/qtopia4.3-snapshot/buildsystem/over-image-prefi
x-and-sdk-location-1.html
There it says that there is possible to use 3 commands for directing
output of Qtopia compilation. -prefix, -sdk and -image
I am using QtopiaCore-4.3.3 and try to run configure
/home/johanh/repository/trunk/xs/qtopia-core-commercial-src-4.3.3/config
ure -embedded arm -qt-mouse-linuxtp -big-endian -depths 8,16,32
-confirm-license -image
/home/johanh/repository/trunk/xs/target/rootfs/usr/local/QtopiaCore
-prefix /usr/local/QtopiaCore -prefix-install
and I get the response invalid command line switch, what am I doing
wrong?
The response
This is the Qtopia Core Desktop Edition.
-image: invalid command-line switch
/home/johanh/repository/trunk/xs/target/rootfs/usr/local/QtopiaCore:
unknown argument
Usage: configure [-prefix <dir>] [-prefix-install] [-bindir <dir>]
[-libdir <dir>]
[-docdir <dir>] [-headerdir <dir>] [-plugindir <dir> ] [-datadir
<dir>]
[-translationdir <dir>] [-sysconfdir <dir>] [-examplesdir <dir>]
[-demosdir <dir>] [-buildkey <key>] [-release] [-debug]
[-debug-and-release] [-shared] [-static] [-no-fast] [-fast]
[-no-largefile]
[-largefile] [-no-exceptions] [-exceptions] [-no-accessibility]
[-accessibility] [-no-stl] [-stl] [-no-sql-<driver>]
[-sql-<driver>]
[-plugin-sql-<driver>] [-system-sqlite] [-no-qt3support]
[-qt3support]
[-platform] [-D <string>] [-I <string>] [-L <string>] [-help]
[-no-zlib]
[-qt-zlib] [-system-zlib] [-no-gif] [-qt-gif] [-no-libtiff]
[-system-libtiff]
[-no-libpng] [-qt-libpng] [-system-libpng] [-no-libmng]
[-qt-libmng]
[-system-libmng] [-no-libjpeg] [-qt-libjpeg] [-system-libjpeg]
[-make <part>]
[-no-make <part>] [-R <string>] [-l <string>] [-no-rpath]
[-rpath] [-continue]
[-verbose] [-v] [-silent] [-no-nis] [-nis] [-no-cups] [-cups]
[-no-iconv]
[-iconv] [-no-pch] [-pch] [-no-qdbus] [-qdbus]
[-no-separate-debug-info]
[-no-mmx] [-no-3dnow] [-no-sse] [-no-sse2]
[-separate-debug-info] [-armfpa] [-no-optimized-qmake]
[-optimized-qmake]
[additional platform specific options (see below)]
Installation options:
These are optional, but you may specify install directories.
-prefix <dir> ...... This will install everything relative to <dir>
(default /usr/local/QtopiaCore)
-hostprefix [dir] .. Tools and libraries needed when developing
applications are installed in [dir]. If [dir]
is
not given, the current build directory will be
used.
* -prefix-install .... Force a sandboxed "local" installation of
Qt. This will install into
/usr/local/QtopiaCore, if this option is
disabled then some platforms will attempt a
"system" install by placing default values to
be placed in a system location other than
PREFIX.
You may use these to separate different parts of the install:
-bindir <dir> ......... Executables will be installed to <dir>
(default PREFIX/bin)
-libdir <dir> ......... Libraries will be installed to <dir>
(default PREFIX/lib)
-docdir <dir> ......... Documentation will be installed to <dir>
(default PREFIX/doc)
-headerdir <dir> ...... Headers will be installed to <dir>
(default PREFIX/include)
-plugindir <dir> ...... Plugins will be installed to <dir>
(default PREFIX/plugins)
-datadir <dir> ........ Data used by Qt programs will be installed
to <dir>
(default PREFIX)
-translationdir <dir>.. Translations of Qt programs will be
installed to <dir>
(default PREFIX/translations)
-sysconfdir <dir> ..... Settings used by Qt programs will be looked
for in <dir>
(default PREFIX/etc/settings)
-examplesdir <dir> .... Examples will be installed to <dir>
(default PREFIX/examples)
-demosdir <dir> ....... Demos will be installed to <dir>
(default PREFIX/demos)
You may use these options to turn on strict plugin loading.
-buildkey <key> .... Build the Qt library and plugins using the
specified
<key>. When the library loads plugins, it will
only
load those that have a matching key.
Configure options:
The defaults (*) are usually acceptable. A plus (+) denotes a default
value
that needs to be evaluated. If the evaluation succeeds, the feature is
included. Here is a short explanation of each option:
* -release ........... Compile and link Qt with debugging turned off.
-debug ............. Compile and link Qt with debugging turned on.
-debug-and-release . Compile and link two versions of Qt, with and
without
debugging turned on. [Mac only]
* -shared ............ Create and use shared Qt libraries.
-static ............ Create and use static Qt libraries.
* -no-fast ........... Configure Qt normally by generating Makefiles
for all
project files.
-fast .............. Configure Qt quickly by generating Makefiles
only for
library and subdirectory targets. All other
Makefiles
are created as wrappers, which will in turn run
qmake.
-no-largefile....... Disables large file support.
+ -largefile.......... Enables Qt to access files larger than 4 GB.
* -no-exceptions ..... Disable exceptions on compilers that support
it.
-exceptions ........ Enable exceptions on compilers that support it.
-no-accessibility .. Do not compile Accessibility support.
* -accessibility ..... Compile Accessibility support.
-no-stl ............ Do not compile STL support.
* -stl ............... Compile STL support.
-no-sql-<driver> ... Disable SQL <driver> entirely.
-qt-sql-<driver> ... Enable a SQL <driver> in the QtSql library, by
default
none are turned on.
-plugin-sql-<driver> Enable SQL <driver> as a plugin to be linked to
at run time.
Possible values for <driver>:
[ db2 ibase mysql oci odbc psql sqlite sqlite2
tds ]
-system-sqlite ..... Use sqlite from the operating system.
-no-qt3support ..... Disables the Qt 3 support functionality.
* -qt3support ........ Enables the Qt 3 support functionality.
-platform target ... The operating system and compiler you are
building
on (qws/linux-x86-g++).
See the README file for a list of supported
operating systems and compilers.
-no-mmx ............ Do not compile with use of MMX instructions.
-no-3dnow .......... Do not compile with use of 3DNOW instructions.
-no-sse ............ Do not compile with use of SSE instructions.
-no-sse2 ........... Do not compile with use of SSE2 instructions.
-D <string> ........ Add an explicit define to the preprocessor.
-I <string> ........ Add an explicit include path.
-L <string> ........ Add an explicit library path.
-help, -h .......... Display this information.
Third Party Libraries:
-no-zlib ........... Do not compile in ZLIB support. Implies
-no-libpng.
-qt-zlib ........... Use the zlib bundled with Qt.
+ -system-zlib ....... Use zlib from the operating system.
See http://www.gzip.org/zlib
-no-gif ............ Do not compile the plugin for GIF reading
support.
* -qt-gif ............ Compile the plugin for GIF reading support.
See also
src/plugins/imageformats/gif/qgifhandler.h
-no-libtiff ........ Do not compile the plugin for TIFF support.
-qt-libtiff ........ Use the libtiff bundled with Qt.
+ -system-libtiff .... Use libtiff from the operating system.
See http://www.libtiff.org
-no-libpng ......... Do not compile in PNG support.
-qt-libpng ......... Use the libpng bundled with Qt.
+ -system-libpng ..... Use libpng from the operating system.
See http://www.libpng.org/pub/png
-no-libmng ......... Do not compile the plugin for MNG support.
-qt-libmng ......... Use the libmng bundled with Qt.
+ -system-libmng ..... Use libmng from the operating system.
See http://www.libmng.com
-no-libjpeg ........ Do not compile the plugin for JPEG support.
-qt-libjpeg ........ Use the libjpeg bundled with Qt.
+ -system-libjpeg .... Use libjpeg from the operating system.
See http://www.ijg.org
-no-openssl ........ Do not compile support for OpenSSL.
+ -openssl ........... Use OpenSSL from the operating system.
Additional options:
-make <part> ....... Add part to the list of parts to be built at
make time.
(libs tools examples demos)
-nomake <part> ..... Exclude part from the list of parts to be
built.
-R <string> ........ Add an explicit runtime library path to the Qt
libraries.
-l <string> ........ Add an explicit library.
-no-rpath .......... Do not use the library install path as a
runtime
library path.
+ -rpath ............. Link Qt libraries and executables using the
library
install path as a runtime library path.
Equivalent
to -R install_libpath
-continue........... Continue as far as possible if an error occurs.
-verbose, -v ....... Print verbose information about each step of
the
configure process.
-silent ............ Reduce the build output so that warnings and
errors
can be seen more easily.
* -no-optimized-qmake ... Do not build qmake optimized.
-optimized-qmake ...... Build qmake optimized.
-no-nis ............ Do not compile NIS support.
* -nis ............... Compile NIS support.
-no-cups............ Do not compile CUPS support.
* -cups .............. Compile CUPS support.
-no-iconv........... Do not compile support for iconv(3).
* -iconv.............. Compile support for iconv(3).
* -no-pch ............ Do not use precompiled header support.
-pch ............... Use precompiled header support.
-no-qdbus........... Do not compile the QtDBus module.
+ -qdbus.............. Compile the QtDBus module.
-reduce-relocations ... Reduce relocations in the libraries through
extra linker
optimizations (Qt/X11 / Qtopia/Core only;
experimental; needs GNU ld >= 2.18)
Qtopia Core only:
-xplatform target ... The target platform when cross-compiling.
-no-feature-<feature> Do not compile in <feature>.
-feature-<feature> .. Compile in <feature>. The available features
are described in
src/corelib/global/qfeatures.txt
-embedded <arch>..... This will enable the embedded build, you must
have a
proper license for this switch to work.
Example values for <arch>: arm mips x86
generic
-armfpa ............. Target platform is uses the ARM-FPA floating
point format.
-no-armfpa .......... Target platform does not use the ARM-FPA
floating point format.
The floating point format is usually
autodetected by configure. Use this
to override the detected value.
-little-endian ...... Target platform is little endian (LSB first).
-big-endian ......... Target platform is big endian (MSB first).
You only need to specify the endianness when
cross-compiling, otherwise the host
endianness will be used.
-no-freetype ........ Do not compile in Freetype2 support.
-qt-freetype ........ Use the libfreetype bundled with Qt.
* -system-libfreetype. Use libfreetype from the operating system.
See http://www.freetype.org/
-qconfig local ...... Use src/corelib/global/qconfig-local.h rather
than the
default (full).
-depths <list> ...... Comma-separated list of supported
bit-per-pixel
depths, from: 1, 4, 8, 16, 18, 24, and 32.
-qt-decoration-<style> ....Enable a decoration <style> in the QtGui
library,
by default all available decorations are
on.
Possible values for <style>: [ styled
windows default ]
-plugin-decoration-<style> Enable decoration <style> as a plugin to
be
linked to at run time.
Possible values for <style>: [ default
windows ]
-no-decoration-<style> ....Disable decoration <style> entirely.
Possible values for <style>: [ styled
windows default ]
-qt-gfx-<driver> ... Enable a graphics <driver> in the QtGui
library.
Possible values for <driver>: [ linuxfb
transformed qvfb vnc multiscreen ]
-plugin-gfx-<driver> Enable graphics <driver> as a plugin to be
linked to at run time.
Possible values for <driver>: [ hybrid qvfb
transformed vnc ]
-no-gfx-<driver> ... Disable graphics <driver> entirely.
Possible values for <driver>: [ linuxfb
transformed qvfb vnc multiscreen ]
-qt-kbd-<driver> ... Enable a keyboard <driver> in the QtGui
library.
-no-kbd-<driver> ... Disable keyboard <driver> entirely.
Possible values for <driver>: [ tty usb sl5000
yopy vr41xx qvfb ]
-qt-mouse-<driver> ... Enable a mouse <driver> in the QtGui library.
Possible values for <driver>: [ pc bus
linuxtp yopy vr41xx tslib qvfb ]
-plugin-mouse-<driver> Enable mouse <driver> as a plugin to be
linked to at runtime.
Possible values for <driver>: [ tslib ]
-no-mouse-<driver> ... Disable mouse <driver> entirely.
Possible values for <driver>: [ pc bus
linuxtp yopy vr41xx tslib qvfb ]
-iwmmxt............. Compile using the iWMMXt instruction set
(available on some XScale CPUs).
+ -no-glib............ Do not compile Glib support.
-glib............... Compile Glib support.
--
[ signature omitted ]
Message 2 in thread
Johan Hedlund wrote:
> I am trying to configure Qtopia according to the instructions on the
> page
> http://doc.trolltech.com/qtopia4.3-snapshot/buildsystem/over-image-prefi
> x-and-sdk-location-1.html
>
> There it says that there is possible to use 3 commands for directing
> output of Qtopia compilation. -prefix, -sdk and -image
>
> I am using QtopiaCore-4.3.3 and try to run configure
Qtopia and Qtopia Core are two different, but related, things. :-/
You need to follow the instructions on this page instead:
http://doc.trolltech.com/4.3/qtopiacore-install.html
Hope this helps,
David
--
[ signature omitted ]
Message 3 in thread
Ok, then perhaps I understand. But I don't understand how to specify where I should install my target cross-compiled libraries. The prefix setting will be the location of development headers and the qmake and so on for a development host which will be copied there when I make install?
Is it possible to install the target cross-compiled librarys to a specified folder with the build system?
/Johan
-----Ursprungligt meddelande-----
Från: David Boddie [mailto:dboddie@xxxxxxxxxxxxx]
Skickat: den 23 januari 2008 16:49
Till: qtopia-interest@xxxxxxxxxxxxx
Ämne: Re: How to configure qtopia?
Johan Hedlund wrote:
> I am trying to configure Qtopia according to the instructions on the
> page
> http://doc.trolltech.com/qtopia4.3-snapshot/buildsystem/over-image-prefi
> x-and-sdk-location-1.html
>
> There it says that there is possible to use 3 commands for directing
> output of Qtopia compilation. -prefix, -sdk and -image
>
> I am using QtopiaCore-4.3.3 and try to run configure
Qtopia and Qtopia Core are two different, but related, things. :-/
You need to follow the instructions on this page instead:
http://doc.trolltech.com/4.3/qtopiacore-install.html
Hope this helps,
David
--
[ signature omitted ]
Message 4 in thread
Johan Hedlund wrote:
> Ok, then perhaps I understand. But I don't understand how to specify where
> I should install my target cross-compiled libraries. The prefix setting
> will be the location of development headers and the qmake and so on for a
> development host which will be copied there when I make install?
>
> Is it possible to install the target cross-compiled librarys to a
> specified folder with the build system?
I think you want the -prefix option but, if you run the configure script
with the --help option, it provides more information about the different
options that can be used to customize the build:
You may use these to separate different parts of the install:
-bindir <dir> ......... Executables will be installed to <dir>
(default PREFIX/bin)
-libdir <dir> ......... Libraries will be installed to <dir>
(default PREFIX/lib)
-docdir <dir> ......... Documentation will be installed to <dir>
(default PREFIX/doc)
[...]
David
--
[ signature omitted ]
Message 5 in thread
Yes I have seen this option and will try to use it. Is it possible when I do the make install just to install my library files for my target platform? I. e. not install my development host files?
/Johan
-----Ursprungligt meddelande-----
Från: David Boddie [mailto:dboddie@xxxxxxxxxxxxx]
Skickat: den 23 januari 2008 17:32
Till: qtopia-interest@xxxxxxxxxxxxx
Ämne: Re: SV: How to configure qtopia?
Johan Hedlund wrote:
> Ok, then perhaps I understand. But I don't understand how to specify where
> I should install my target cross-compiled libraries. The prefix setting
> will be the location of development headers and the qmake and so on for a
> development host which will be copied there when I make install?
>
> Is it possible to install the target cross-compiled librarys to a
> specified folder with the build system?
I think you want the -prefix option but, if you run the configure script
with the --help option, it provides more information about the different
options that can be used to customize the build:
You may use these to separate different parts of the install:
-bindir <dir> ......... Executables will be installed to <dir>
(default PREFIX/bin)
-libdir <dir> ......... Libraries will be installed to <dir>
(default PREFIX/lib)
-docdir <dir> ......... Documentation will be installed to <dir>
(default PREFIX/doc)
[...]
David
--
[ signature omitted ]
Message 6 in thread
Johan Hedlund wrote:
> Yes I have seen this option and will try to use it. Is it possible when I
> do the make install just to install my library files for my target
> platform? I. e. not install my development host files?
I guess the way to do it would be to customize the paths so that the header
files are simply copied somewhere different to the library files. I don't
think you can disable installation of certain files, but this isn't my area
of expertise.
David
--
[ signature omitted ]
