Welcome to devpaks repository

Rules for creating devpaks

Revision 2

Please note that this is very young version of this document. If you have any comments or proposals or opinions tell them us in this discussion.

File naming rules

If your devpak is independent on GCC version (typically plain C devpaks), you should follow this rule:

program_name-version-package_revision.DevPak

Name of the package and version cannot contain - use _ instead. Example:

If your devpak depends on GCC version (C++ devpaks) the rules looks like this:

program_name-version-gccversion-package_revision.DevPak

Example:

Package revision explained

Package revision part consists of build number and packager identifier. E.g. third release of Allegro 4.1.16 devpak packed by Michal Molhanec would have the name:

allegro-4.1.16-3mol.DevPak

Don't use mol for your devpaks. Choose your own identifier!

Where to install files

What Where
header files <app>\include\
library files (lib*.a) <app>\lib\
documentation <app>\docs\<LibraryName>\
binary files <app>\bin\
DLL files <app>\bin\ optionally also into <sys>\
examples <app>\examples\<LibraryName>\

Other rules

Don't use unnecessary lib prefix for devpak name, only when it is part of the official library name. E.g. libpng is name of the library so it makes sense to call the devpak libpng. On the other hand it makes no sense to call Allegro devpak liballegro instead of just allegro.