I’m in the process of writing a DevPak for the libharu libary. These are actually tar.bz2 packages of whatever you think is a good idea to install into the Dev-C++, Code::Blocks or wxDev-C++ IDEs. E.g. precompiled libraries and necessary header files. In addition one adds a so called DevPackage file, which tells the IDEs where to put all the files. Since you are also allowed to install files into the windows directory, these packages are also quite dangerous – you should check the package content first (rename xxx.DevPak to xxx.tar.bz2). The DevPackage file format is more or less straight forward, but first I couldn’t find a documentation for that. In the cvs repository of Dev-C++ there was actually a documentation (File Format.txt), but it contained some errors. So I updated the file and make it available in this post. Continue reading Instructions on how to create DevPak packages
I regularly make backups of all my data, it’s also synchronized on several computers and hard disks. But since I backup only once a week, I don’t really have several revisions from files available between the backups. This is espacially necessary if you work on some code of a small project, which is not revisioned via svn or cvs – and you don’t want to or have no access to svn. Also you don’t want to set up a local svn or cvs repository. You could use Time Machine on Mac OS X and there are some other tools available on Windows, like FileHamster. But FileHamster wasn’t always trouble free and by coincidence I found another solution which is rather appealing: Mercurial.
The nice thing about Mercurial is, that it is a fast, distributed, lightweight Source Control Management system – you don’t need a server for it. The revisions are save to the local .hg folder. In this post I just explain some basics to get started (on Windows – but apart from the installation process, it’s the same for Mac OS X and Linux).