Now that I managed to build full TDE source, as well as a single module in isolation, I want to figure out how to quick rebuilds. By "quick rebuilds" I mean being able to avoid installing the dependencies every single time, as well as skiping building of deb packages. In other words, I want to be able to quickly check whether the code compiles at all.
Going back to the email from 25th October:
There are two main ways of working:
- locally in your computer
Here you build packages in your environment, so you don't have to wait for dependencies to be downloaded and the build is quicker. This is ideal for prototyping, testing, debugging and so on. Depending on what you are working on, occasionally you may end up with weird results, but 99.5% of the time you will be fine. Recommended workflow (refer to readme.txt file):
- ./build_module.sh -g -po <module name> --> prepare the code in a build folder
- switch to the created build folder for the module
- debian/rules clean, followed by debian/rules binary --> builds all the debian binary
packages, locally
- for specific subpart of big modules (like tdelibs, tdebase, ...) you can "cd obj..." and then
use specific ninja targets for partial builds.
If you build locally, you can just build a single module, provided the required dependencies are installed.
I'm having issues with this. Running `debian/rules binary` results in a bunch of warnings about missing files, and then fails with an error. See attached log. I presume there are some additonal preparation steps that need to be taken here? I tried installing via apt all the PSB packages listed as dependencies by amarok, but that does not resolve the problem.
Cheers, Janek