Application development for KolibriOS. Overview of options

What you need to start developing for Hummingbird OS (CBS)?

• A forum to know which direction to go;
• Wiki, although unfortunately quite fragmented, but will give the necessary minimum of overview information;
• Sources for programs in the Subversion repository (SVN);
• Handbook of system functions in Russian and English SVN: /kernel/trunk/docs/sysfunc*.txt , or on the wiki ;

What to use for development and what is needed for this:

1. Prepare a working environment or machine to run the system. You can work on a live gland (possibly with hardware support problems). Personally, I run the OS in a free for non-commercial use of VMware Player, but the Hummingbird works in QEMU and in VirtualBox, and in the Bochs emulator.
   ')
   Install the SVN client by choice - for example, for the command line there is SlikSVN , visual RapidSVN , SubTile (you need Firefox runtime), but there is in the form of the Windows Exporer TortoiseSVN extension.
   We are looking for a complete tutorial on working with SVN on the net, here are examples of typical commands for SlikSVN, being in the right directory:
   
   

   > svn co svn://kolibrios.org/contrib/sdk sdk - get yourself an up-to-date copy;
   > svn status --show-updates - show svn status --show-updates — view files that have been changed compared to the server;
   > svn up - update your copy from the server;
   > svn add *.c - add all new c-files under control;
   > svn commit --username XXXX --password YYYY -m " " - upload your changes to the server (first, do not forget to analyze the status);

   
   No password is required to download source files from SVN. You can use the SVN server's web capabilities to view the Hummingbird code and applications, but you cannot see the Russian-language comments in CP1251 encoding (CP866 is supported).
   
   
2. The FASM assembler and Tinypad editor come with the installed system, which is natural for a system written in Assembler. Directly from the editor, you can open the system functions guide, Board debug message board, broadcast the program and run it independently or in the Mtdbg system debugger. An example of the program is also in the ISO image, you can still watch programs on SVN on the SVN path: / programs / demos.
   
   
3. C--. The second native language for this system, in which many system utilities are written. It is similar to C, but instead of the standard C-library it uses direct system calls and allows you to work with processor registers directly, due to which the program is more compact. Lying here , examples of programs, very nicely written by the way - SVN: / programs / cmm. SVN Library: / programs / cmm / lib. There is a Hummingbird working and cross compiler for Windows. About him there is a more detailed article on Habré from Punk_Joker
   
   
4. Cross compiler C / C ++ GCC. Host can be Linux or Windows. It lies here , you need to download msys-kos32 or linux-kos32 and SDK with ready C-libraries for CBS. Some required to run GCC dll under Windows may have to be downloaded separately from the mingw page , if you don’t have it on the machine yet. It uses the newlib library modified for CBS, which needs to be downloaded from SVN: / contrib / sdk / sources / newlib (libstdc ++ - v3 is also nearby). In the SDK there is a pre-assembled libc.dll for dynamic loading, and for a static link, the library will have to be built by yourself.
   
   The only inconvenience of cross-compilation is that every time you need to copy the resulting program to the system. The options are either via FTP if the server works with your network card, or via a USB flash drive, or by modifying the ISO image of the system (for example, using Magic ISO Maker) and restarting it. On this compiler there is an article on Habré from pascualle , from which you can take a makefile. In the near future (already in the test) release of the gcc 5.4 port from ion2
   
   
5. A simple TinyC compiler in the form of a native and cross-compiler for Windows (you can build for Linux). Take the complete set with examples here , the easiest way to copy it with the program in the Hummingbird and use it there. It supports only pure C, with the support of some language extensions from GCC, for example, attributes and assembly inserts.

Compile and debug

• gcc (static libc) - lines are complex, therefore it is better to use ready-made makefiles
  
  

  > kos32-gcc -c -g -U__WIN32__ -U_Win32 -U_WIN32 -U__MINGW32__ -UWIN32 -I $(SDK_DIR)/sources/newlib/libc/include -o hello hello.cpp - normal compilation
  
  > kos32-ld -static -nostdlib -T $(SDK_DIR)/sources/newlib/static.lds -Map=hello.map -L $(SDK_DIR)/lib -L /home/autobuild/tools/win32/mingw32/lib -o hello hello.o -lstdc++ -lsupc++ -lgcc_eh -lc -lapp -lgcc -lc - link with the proper format for the Hummingbird and the creation of a .map file for the debugger
  
  > kos32-objdump -d -M intel -S hello.o > hello.asm - create an assembly file with the lines of the source cpp file for convenience
  > kos32-objcopy hello -O binary - cutting off the excess and generating the Hummingbird executable file

  
  It is a bit difficult, but as a result of the map file, we can look at the physical addresses of the data and functions and see the correspondence between the assembler and C-code.
  
  
• GCC (libc in the form of .dll) - the difference from the static assembly only in the link line:
  
  

  > kos32-ld -static -S -nostdlib -T $(SDK_DIR)/sources/newlib/app.lds --image-base 0 -Map=hello.map -L $(SDK_DIR)/lib -L /home/autobuild/tools/win32/mingw32/lib -o hello hello.o -lstdc++ -lsupc++ -lgcc_eh -lc.dll -lapp -lgcc -lc.dll

• Tinyc
  

  > tcc hello.c -o hello -lck -g

  
  Everything is easier here, since the compiler is modified specifically for Hummingbirds.

More exotic options, but which may seem comfortable to you:

1. Use other C compilers or languages ​​according to this article .
   When reviewing examples of C programs, please pay special attention to the fact that the system uses different libc programs in different programs, developed in different historical eras, characterized by system API calls:
   
   
   • The old menuetlibc, inherited from the menuetOS ancestor, <menuet / os.h>, is prefixed with functions __menuet, is a DJGPP port. It is often used with GCC, although I would consider it obsolete and advised to use the new newlibc <kos32sys.h>.
     
   • Tcc has its own simplified libck, but API calls <kos32sys1.h> are unified with GCC. Although there is still an old tcc version of <kolibrisys.h>, I personally did not test it.
   • minimum feature set for MSVC. It is determined by the files "kosSyst.h", "KosFile.h". Outdated
   • minimum set of functions for for BCC “menuet.h”
   • pretty complete library for WatcomC “kolibri.h”
   
   
2. Use Oberon. It's like standard Pascal, only better, and syntax simpler than Object Pascal (Delphi). Language description takes only 13 pages. The compiler and documentation here , an example of use is fbreader . By the way, while this article was being prepared, the author of the compiler has already done an article about using Oberon. Expect soon.
   
   
3. There are also ports PascalPro , the ability to use FreePascal, TinyPy , Lua , Forth , Basic of varying degrees of readiness. Perhaps these topics will be disclosed in separate articles.

More on creating application programs

Development of console applications:

• use shell.c functions
• use API for IPC (interprocess communication), SysFn 60
• use API for Shared Memory, SysFn 68.22
• use Clipboard API, Clipboard, SysFn 54.1

Graphic Application Development:

 #define MEMSIZE 4096*10 #include "../lib/io.h" #include "../lib/gui.h" void main() { word id; dword file; io.dir.load(0,DIR_ONLYREAL); loop() switch(WaitEvent()) { case evButton: id=GetButtonID(); if (id==1) ExitProcess(); break; case evKey: GetKeys(); if (key_scancode == SCAN_CODE_ESC ) ExitProcess(); break; case evReDraw: draw_window(); break; } } void draw_window() { proc_info Form; int i; DefineAndDrawWindow(215,100,350,300,0x34,0xFFFFFF,"Window header"); GetProcessInfo(#Form, SelfInfo); for (i=0; i<io.dir.count; i++) { WriteText(5,i*8+3,0x80,0xFF00FF,io.dir.position(i)); } DrawCaptButton(100, 10, 100, 22, 22, 0xCCCccc, 0x000000, "Button"); WriteText(100,50,0x80,0,"Textline small"); WriteText(100,70,0x90,0,"Textline big"); DrawBar(100, 110, 100, 100, 0x66AF86); }