2015-09-20 14:41 GMT+02:00 Gregor Riepl <onit...@gmail.com>: >> The doc source is available at https://github.com/kicad/kicad-doc >> >> It takes quite some time to build with asciidoc, so you might want to >> fetch the precompiled docs from http://docs.kicad-pcb.org/ > > Thanks, Nick. > > I'm not strongly familiar with the DFSG rules concerning documentation, but I > would assume that the main concern is that documentation needs to be available > in "source" form. Building the documentation from its sources upon packaging > would guarantee that, and it's a do-once process so time is not a concern. > > More importantly, how do all these sub-packages tie into the build process? > I assume that the main kicad CMakeFiles will only build kicad itself, and not > pick up additional subdirectories like kicad-i18n, kicad-doc, kicad-library or > library-repos. The current Debian packaging scripts will simply copy the > appropriate files out of doc/ and library/ to form the various packages. This > process will need to be changed if sub-repositories like the documentation > require their own build process.
You should just build kicad first, then build the kicad-i18n with the same cmake prefix. You can have multiple sources for a package without problems. What do you mean that it will copy the appropiate fiels out of doc and library? > Alternatively, the documentation could be moved out-of-tree and built with the > help of separate dpkg scripts. The important parts that form the kicad and > kicad-common packages are in kicad, kicad-i18n, kicad-library and the *.pretty > repositories if I'm not mistaken. What is the kicad-common package supposed to provide? > On another note, Nick, I think the _*.kiface plugins should be moved to > <prefix>/lib/kicad/kiface or something. <prefix>/bin is not an appropriate > place for them, as they are not executables. Should I file a bug on Launchpad > for that? I think that might be the best action to do.
