Developer FAQ
Frequently asked questions about developing for ProteanOS.
Frequently Asked Questions
How do I start developing for ProteanOS?
Begin with the Development Hub for an overview, then set up ProKit and familiarize yourself with the build process. The development mailing list is a good resource for questions.
What development tools do I need?
You need ProKit (the development kit), standard build tools (GCC, make), and familiarity with cross-compilation concepts for embedded development.
Is there a development environment image?
ProKit provides the development environment setup. Follow the ProKit documentation to configure your development system.
Packaging Questions
Frequently Asked Questions
What package format does ProteanOS use?
ProteanOS uses the OPK package format. Source packages follow the Source Package Format 2.0 specification, which defines control files, build rules, and metadata structure.
How do I create a new package?
Create a source package following SPF 2.0, including control file, rules file, and other required metadata. Use ProKit build tools to compile and package.
How are dependencies handled?
Dependencies are declared in the control file using defined syntax. The package manager (opkg) resolves and installs dependencies automatically.
What about architecture-specific packages?
The multi-architecture system allows packages to be built for different target architectures. Declare architecture requirements in package metadata.
Build System
Frequently Asked Questions
How does cross-compilation work?
ProKit sets up the cross-compilation toolchain and environment variables. Build rules in your package are executed in this cross-compilation context.
Can I build natively on target hardware?
While possible on some platforms, cross-compilation is generally recommended for embedded development due to resource constraints on target devices.
How do I test my package?
Install the built package on target hardware or in an emulated environment. Use standard testing practices and verify functionality before submission.
Contributing
Frequently Asked Questions
How do I submit a patch?
Prepare patches using git format-patch and send them to the development mailing list. Include a clear description of changes and rationale.
What coding standards should I follow?
Follow existing code style in each project. Generally, clear, well-documented code that follows Unix conventions is expected.
How long does patch review take?
Review time varies based on complexity and reviewer availability. Simple fixes may be reviewed quickly; larger changes require more discussion.
More Resources
For detailed development information, see:
- Development Hub — overview of development resources
- ProKit documentation — development kit guide
- Source Package Format 2.0 — packaging specification
- Git repositories — source code access