2015-09-21 12:42 GMT+02:00 Gregor Riepl <onit...@gmail.com>: >>> 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? > > The existing build process is slightly quirky. > First, it executes cmake, make and make install in the main kicad source tree. > This will build kicad for a /usr/local/bin prefix (I want to change that > later), then install it into a temp dir.
Why don't you use -DCMAKE_PREFIX_PATH=/usr or whatever path you want? > Then, it uses a debian/*.install file > for each package to move files into their correct place. In the case of > kicad.deb, this will replace usr/local with usr. kicad-common does the same > for installed arch-independent files, but also copies various files directly > out of the source tree. Among those are the libraries and the *.po files. > Lastly, each kicad-doc-<lang>.install lists the PDF files to be copied out of > the doc directory. > > Since the new repositories (except the *.pretty ones) all contain cmake > scripts, it may be better to just use those to install the i18n, docs and > libraries. I know that the docs cmake stuff is not really prepared to install properly to the locations searched by KiCad, IIRC. >> What is the kicad-common package supposed to provide? > > Currently, it contains: > - The usual Debian /usr/share/doc/<package>/ stuff > - *.desktop files, MIME type associations and icons > - i18n -> /usr/share/kicad/internat (probably the wrong place) Well, this is where KiCad expects to find the po files. That it might not be the best place it another matter. > - scripts -> /usr/share/doc/kicad/scripts (including the shell scripts) > - libraries and modules -> /usr/share/kicad/[library|modules] > > I'd like to include the pretty repositories as well. It seems cvpcb will not > work without them, and it would be nice to have everything set up without > requiring another download after KiCAD is launched for the first time. > >>> 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. > > Done, https://bugs.launchpad.net/kicad/+bug/1497945 >
