Development

• Eigene Programme kompilieren
• Cross-Compiler / Toolchain erstellen
  • There are some general pre-requisite to meet:
  • Now you have only to create the according target compiler and libraries
  • Using the linux configure mechanism on the box needs some further things to do
  • Using the dev-tools package to install compiler and tools
• Device Table
  • Regular directories
  • Regular files
  • System devices
  • MTD stuff
  • Tun/tap driver
  • coda driver
  • bluez
  • autofs4
  • SCSI Devices
  • Proprietary devices
  • Fritzbox 7340
• Freetz Build-Prozeß
  • Vorwort und Motivation
  • Grundsätzliches
  • Was tut make?
  • Woraus besteht Freetz?
  • Ablauf des Build-Prozesses
  • Include-Kette
  • Sonstige Make-Targets
• List of kernel sources [EN]
  • Table like overview
  • Tree like overview
• Menükonfiguration pflegen
  • Einstieg
  • Syntax-Fehler in MK-Dateien finden
  • Syntax-Hervorhebung für MK-Dateien
• Package Developing - Advanced Topics [EN]
  • Adding conditional patches
  • Adding multi-binary packages
• Package Development [EN]
  • Persistent Package Settings
  • Custom package saving mechanism
• Package development config [EN]
• libmodcgi.sh
  • cgi
  • cgi_begin
  • cgi_end
  • sec_begin
  • sec_end
  • html
  • check, select
  • href
  • back_button
  • sec_level
  • stat_bar
  • cgi_param
  • cgi_error, print_error
  • path_info
  • valid
• Makefiles [EN]
• Example 1: Httptunnel [EN]
  • Build manually
  • Add package to Freetz
  • Use of the “empty” Package as Starting Point
  • Call Procedures “make menuconfig” and “make”
  • Testing
  • Preparing New Package for Public Integration to Freetz Trunk
• Example 2: par2cmdline [EN]
  • Build manually
  • Add package to Freetz
  • Create new image with added package
  • Testing
  • Preparing New Package for Public Integration to Freetz Trunk
• Example 3: NZBGet [EN]
  • Build manually
  • Add package to Freetz
  • Create new image with added package
  • Testing
  • Preparing New Package for Public Integration to Freetz Trunk
• Wie baue ich ein eigenes Paket für Freetz?
• First steps - How to start your first freetz package [EN]
  • Info
  • Build Environment
  • Toolchain
  • File Structure
  • Examples Binary Package
  • Configuration Handling
  • Examples Web-Interface
  • Trouble shooting
  • References
• Erstellen einer GUI für Pakete in Freetz
  • Motivation
  • Grundlagen
  • Eigene Pakete
  • Konfiguration
  • Wie funktioniert das mit der GUI?
  • Ein Beispiel
• Web-interface HTTPTunnel [EN]
  • httptunnel.cfg
  • httptunnel.cgi
  • rc.httptunnel
  • Test on router
  • References
• Aufbau eines Patches
  • Erzeugen eines Patches
  • Patch anwenden oder rückgängig machen
  • Wie finde ich die zu patchende Stelle?
  • Links
• Shell Language [EN]
  • Basic Format
  • If, For, and While
  • Test Built-in
  • Single-line conditional statements
  • Infinite Loops
  • Exit Status and If/While Statements
  • Variable References
  • Variable Naming
  • Quoting
  • Variable Assignments
  • Testing for (Non-)Empty Strings
  • Commenting
  • Pathnames
  • Interpreter Magic
• SquashFS 4 (BE) [EN]
• STARTLEVEL of packages [EN]
• UI-Module und ctlmgr_ctl
  • Module
  • Keys
  • Alle Variablen
  • Variable lesen
  • Variable schreiben
  • Mehrere Variablen
  • Listen
  • Links

This site is open source. Improve this page.