Developing
From OESF
(Difference between revisions)
Line 1: |
Line 1: | ||
| - | + | This section contains various howtos on Zaurus software development and compilation. You should first read [[Special Considerations]] for some good things to keep in mind before getting started with development. | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | == Cross Compiling Information == | |
| + | |||
| + | Cross compiling refers to building software for the Zaurus on a non-Zaurus, non-Arm based system, usually a PC, as opposed to compiling on the Zaurus itself. The advantage to this approach is that such systems are usually faster and have more Memory and Storage space. | ||
[[Compiler Setup]] | [[Compiler Setup]] | ||
| - | [[ | + | [[Cross compiling (non-Qtopia) tips]] |
| - | + | Cross Compiling on OSX - | |
| + | # http://www.lucid-cake.net/osx_arm/index_en.html | ||
| + | # http://www.dsitri.de/wiki.php?page=Zaurus-X-gcc | ||
| - | [ | + | * see also [http://kopsisengineering.com/kopsis/SharpZaurusSdkDsl Zaurus Development with D*** Small Linux] |
| + | * see also [http://linuxdevices.com/articles/AT6830035793.html Cross Compiling] | ||
| - | + | == On-board Compilation == | |
| - | + | If you still want to compile on the Zaurus itself | |
| - | [[ | + | [[How to compile on the 6000L]] |
| - | + | == Kernel Compilation == | |
| - | [[ | + | [[Compiling the Kernel]] |
| + | |||
| + | [[Compiling the Kernel for the SL-C700 with IPv6 Support]] | ||
| + | |||
| + | == Zaurus hardware/OS-specific programming tips == | ||
[[Buzzer Howto]] | [[Buzzer Howto]] | ||
Line 34: |
Line 37: | ||
[[Audio Howto]] | [[Audio Howto]] | ||
| - | |||
| - | [[Fullscreen Howto]] | ||
[[Resume Event]] | [[Resume Event]] | ||
| + | |||
| + | [[Turning off the screen]] | ||
| + | |||
| + | [[System Layout]] | ||
| + | |||
| + | [[Run Levels]] | ||
| + | |||
| + | |||
| + | == Qtopia == | ||
| + | |||
| + | [[Fullscreen Howto]] | ||
[[Keys]] | [[Keys]] | ||
| - | [[ | + | [[Application Help Files]] |
| - | + | [[Sharp Qtopia QCop Messages]] | |
| - | + | ||
| - | + | ||
| - | [ | + | * see also [http://www.trolltech.com/training/index.html Qt and Qtopia Training] |
| + | |||
| + | == Creating IPKGs == | ||
| + | |||
| + | [[IPKG Howto]] | ||
| + | |||
| + | [[Checklist]] | ||
| + | |||
| + | == Application Specific == | ||
| + | |||
| + | [[DTM database]] | ||
[[MySQL server on the Z]] | [[MySQL server on the Z]] | ||
| - | + | == Other sources of information == | |
| - | [[ | + | For developing in languages other than C, or other OS environments |
| + | |||
| + | * see also [[Unofficial Zaurus FAQ]], especially the [[Programming]] section | ||
| + | * see also [http://oe.handhelds.org/cgi-bin/moin.cgi/GettingStarted Getting Started with OE] | ||
| + | |||
| + | * see also [[Zaurus_Java_FAQ]] | ||
| + | * see also [[Playing with Python]] | ||
Revision as of 15:45, 6 April 2006
This section contains various howtos on Zaurus software development and compilation. You should first read Special Considerations for some good things to keep in mind before getting started with development.
Contents |
Cross Compiling Information
Cross compiling refers to building software for the Zaurus on a non-Zaurus, non-Arm based system, usually a PC, as opposed to compiling on the Zaurus itself. The advantage to this approach is that such systems are usually faster and have more Memory and Storage space.
Cross compiling (non-Qtopia) tips
Cross Compiling on OSX -
- see also Zaurus Development with D*** Small Linux
- see also Cross Compiling
On-board Compilation
If you still want to compile on the Zaurus itself
Kernel Compilation
Compiling the Kernel for the SL-C700 with IPv6 Support
Zaurus hardware/OS-specific programming tips
Qtopia
- see also Qt and Qtopia Training
Creating IPKGs
Application Specific
Other sources of information
For developing in languages other than C, or other OS environments
- see also Unofficial Zaurus FAQ, especially the Programming section
- see also Getting Started with OE
- see also Zaurus_Java_FAQ
- see also Playing with Python

