Compiling tips

I usually put that long configure command I mentioned above into a file called conf and leave it in my CVS directory. Then I can do a ../conf from any module and get a good configure.

Sometimes compiling a module takes very long and you'll want to exclude some subdirectories from compilation. Let's assume that you don't want to build the kmail and korganizer applications, located under the kmail and korganizer subdirectores respectively. In that case you can run:

DO_NOT_COMPILE="kmail korganizer" ./configure

which will exclude the kmail and korganizer subdirectories from the build process.

Alternatively you can put the subdirs you want to have compiled into a file called inst-apps in the toplevel directory of a module.

If you are working on modules with strong interdepencies, as f.ex. the kdepim module depending on the latest kdelibs from CVS HEAD, you should make sure to check out all the modules at the same time. Otherwise you risk finding out while compiling that the module depends on recent features of another module. Then you update the other module only to find out that the previous module doesn't compile any more because an API that it depends on API changed ... When you check out all the modules you neeed at the same time your chance is higher that they'll be in a consistent state.