You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
90 lines
4.3 KiB
90 lines
4.3 KiB
14 years ago
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||
|
|
<!-- /home/espenr/tmp/qt-3.3.8-espenr-2499/qt-x11-free-3.3.8/doc/embporting.doc:36 -->
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||
|
|
<title>Issues to be aware of when porting Qt/Embedded</title>
|
||
|
|
<style type="text/css"><!--
|
||
|
|
fn { margin-left: 1cm; text-indent: -1cm; }
|
||
|
|
a:link { color: #004faf; text-decoration: none }
|
||
|
|
a:visited { color: #672967; text-decoration: none }
|
||
|
|
body { background: #ffffff; color: black; }
|
||
|
|
--></style>
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
|
||
|
|
<table border="0" cellpadding="0" cellspacing="0" width="100%">
|
||
|
|
<tr bgcolor="#E5E5E5">
|
||
|
|
<td valign=center>
|
||
|
|
<a href="index.html">
|
||
|
|
<font color="#004faf">Home</font></a>
|
||
|
|
| <a href="classes.html">
|
||
|
|
<font color="#004faf">All Classes</font></a>
|
||
|
|
| <a href="mainclasses.html">
|
||
|
|
<font color="#004faf">Main Classes</font></a>
|
||
|
|
| <a href="annotated.html">
|
||
|
|
<font color="#004faf">Annotated</font></a>
|
||
|
|
| <a href="groups.html">
|
||
|
|
<font color="#004faf">Grouped Classes</font></a>
|
||
|
|
| <a href="functions.html">
|
||
|
|
<font color="#004faf">Functions</font></a>
|
||
|
|
</td>
|
||
|
|
<td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><h1 align=center>Issues to be aware of when porting Qt/Embedded</h1>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<p> Qt/Embedded is designed to be reasonably platform-independent. The
|
||
|
|
only publically available version is a Linux implementation. The
|
||
|
|
following dependencies will need to be addressed if you intend to port
|
||
|
|
to another operating system (files that you need to modify are listed
|
||
|
|
at the end of each section):
|
||
|
|
<p> <ul>
|
||
|
|
<p> <li> <b>System V IPC</b> (shared memory and semaphores) is used to share
|
||
|
|
window regions between client and server. You will need to provide
|
||
|
|
something similar unless you want a single-application setup (i.e.
|
||
|
|
running only one program, which is the server). System V semaphores
|
||
|
|
are also used for synchronising access to the framebuffer.
|
||
|
|
<p> Modify <tt>qwindowsystem_qws.cpp</tt>, <tt>qwsregionmanager_qws.cpp</tt>, <tt>qapplication_qws.cpp</tt>, and <tt>qlock_qws.cpp</tt>.
|
||
|
|
<p> <li> <b>Unix-domain sockets</b> are used to communicate things like
|
||
|
|
keyboard events, requests to raise windows and QCOP messages between
|
||
|
|
applications. Again, you will need to provide something similar unless
|
||
|
|
you want a single-application setup. It should be possible to
|
||
|
|
implement something like this using message queues or similar
|
||
|
|
mechanisms; with the exception of QCOP messages (which are generated
|
||
|
|
by client applications and not Qt/Embedded) individual messages should
|
||
|
|
be no more than a few bytes in length.
|
||
|
|
<p> Modify <tt>qwssocket_qws.cpp</tt>.
|
||
|
|
<p> <li> <b>The Linux framebuffer device</b> is used to map in the drawing
|
||
|
|
area. You will need to replace it (by creating a new class of <a href="qscreen.html">QScreen</a>)
|
||
|
|
with something else giving a byte pointer to a memory-mapped
|
||
|
|
framebuffer, plus information about width, height and bit depth (which
|
||
|
|
most likely you can simply hard-code). If your framebuffer is not
|
||
|
|
memory-mapped or is in an unsupported format or depth you will need to
|
||
|
|
modify QGfxRaster as well.
|
||
|
|
<p> Modify <tt>qgfxlinuxfb_qws.cpp</tt>.
|
||
|
|
<p> <li> <b>The accelerated drivers</b> currently use the Linux QScreen and use
|
||
|
|
<tt>/proc/bus/pci</tt> to map in PCI config space. However, these are only
|
||
|
|
example drivers; you will probably need to write your own driver in
|
||
|
|
any case, and you will need to provide your own way to map in control
|
||
|
|
registers.
|
||
|
|
<p> Modify <tt>qgfxmach64_qws.cpp</tt>, <tt>qgfxvoodoo_qws.cpp</tt> and <tt>qgfxmatrox_qws.cpp</tt>.
|
||
|
|
<p> <li> <b>Sound</b> uses a Linux <tt>/dev/dsp</tt> style device. If you want to use
|
||
|
|
the Qt/Embedded sound server you'll need to reimplement it.
|
||
|
|
<p> Modify <tt>qsoundqss_qws.cpp</tt>.
|
||
|
|
<p> <li> <b>select()</b> is used to implement QSocketDevices and listen for
|
||
|
|
events to/from the Qt/Embedded server application.
|
||
|
|
<p> Modify <tt>qapplication_qws.cpp</tt>.
|
||
|
|
<p> </ul>
|
||
|
|
<p> Qt/Embedded makes use of the standard C library and some Posix functions.
|
||
|
|
Mostly the latter are concentrated in platform dependent code anyway
|
||
|
|
(e.g. mmap() to map in the Linux framebuffer).
|
||
|
|
<p>
|
||
|
|
<!-- eof -->
|
||
|
|
<p><address><hr><div align=center>
|
||
|
|
<table width=100% cellspacing=0 border=0><tr>
|
||
|
|
<td>Copyright © 2007
|
||
|
|
<a href="troll.html">Trolltech</a><td align=center><a href="trademarks.html">Trademarks</a>
|
||
|
|
<td align=right><div align=right>Qt 3.3.8</div>
|
||
|
|
</table></div></address></body>
|
||
|
|
</html>
|