Developing
From OESF
(→Cross Compiling Information) |
m (→Zaurus hardware/OS-specific programming tips) |
||
Line 30: |
Line 30: | ||
== Zaurus hardware/OS-specific programming tips == | == Zaurus hardware/OS-specific programming tips == | ||
| + | |||
| + | [[SDL]] - Using the Zaurus ports of the SDL library | ||
[[Buzzer Howto]] | [[Buzzer Howto]] | ||
Line 46: |
Line 48: | ||
[[Run Levels]] | [[Run Levels]] | ||
| - | |||
== Qtopia == | == Qtopia == | ||
Revision as of 14:58, 2 May 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
- see also How Do You Do that in Linux - Lots of specific examples of cross-compilation
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
SDL - Using the Zaurus ports of the SDL library
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
