<snip>
We can place those build options on the wiki. I likely would add lots of commentation in my build scripts too.
Sounds good.
Yes, I can run configure --help before every build, but I'm not a developer with years of experience in that area. I do not know what to look for or necessarily recognize what I read. I can write, but I need guidance as to what needles I am looking for and in what haystacks.
Regarding building kdepim.
Successfully built.
I have no explanation. I installed libcaldav but not libcardav because we don't know know yet why that package does not compile. With libcaldav installed the kdepim package compiled for the first time.
Weird. The build log you sent me failed in a location that does not even touch lib*dav. You might want to ensure that your previous failure without libcaldav installed wasn't just some kind of fluke. Definitely try without the -j4 flag and see what happens.
Yet as my previous message stated, without libcaldav the build fails.
Of course, to be considered bug-free with respect to compiling, we need to be able to compile with or without the lib*dav packages.
Agreed.
If you support enabling/disabling various options, then compiling needs to test those variations.
Yes it does.
I still have made no headway with the other three packages: kdebindings, koffice, and kdemultimedia. Of course, all of them require significant time to compile. Each FTB is discouraging because of the time required.
Those three are not simple to fix. With kdebindings I don't understand the build system well enough to fix it right away. koffice is because the wv2 library does not provide a .la file, which you will either have to figure out why it doesn't, or building koffice may have to wait until the build system is ported over to CMake. A third possibility would be if you can find an option to disable the word import filter that utilizes the wv2 library.
With respect to kdemultimedia, that is what I will look at next.
Tim