@jens: Hey mate, since you are using GNU / Linux, you might help me a bit.
I use GNU / Linux Fedora 12 (and soon 13), and I would like to do everything I do under Windows at work.
I update Code::Blocks using svn (either through RapidSVN or command line itself), open it with Code::Blocks stable edition; if everything works OK, I run
update.bat and everything synchronizes smoothly.
Now about GNU / Linux. I have opened
update script (for GNU / Linux systems) to see the differences from Windows batch file and saw that it does not do exactly the same things as
update.bat.
I find it irritating all the time to run commands like
- ./boostrap
- ./configure --with-contrib-plugins=all
- make
- su -c 'make install'
whereas I have available
CodeBlocks-unix.cbp and
ContribPlugins-unix.workspace, and I compile everything just fine. What I did this time was to run the whole process as I usually do, and run afterwards
./update script. I can see that it has generated a
run.sh script and by running it, it gives me the chance to test my application. What about an update command so I may avoid the previous painful procedure?
Shouldn't
update script do exactly the same thing like
update.bat?
Please advice.