Alright so I've been working on getting automated Docker container builds going, and I've run into a hiccup. As you mentioned, machinekit-cnc needs files from machinekit-hal to build, and the approach that I am taking to solve the problem is to build Docker containers for machinekit-cnc using the ones for machinekit-hal as a base, and installing the Debian packages generated from the mk-hal build into the mk-cnc containers. Here is where I run into a problem. The build needs header files that are provided by the machinekit-hal-dev package, which depends on machinekit-hal, but both packages provide /usr/bin/comp. When installing via apt-get install, apt detects that machinekit-hal-dev tries to overwrite /usr/bin/comp from machinekit-hal and aborts the install. This behavior can be mitigated for non sys_root environments by passing -o Dpkg::Options::="--force-overwrite" to apt. However, when those two packages are specified in a multistrap config, multistrap fails silently and does not install any of the machinekit packages.
I am not very familiar with Debian packaging, but noticed that the file debian/machinekit-hal.install in the mk-hal repo contains the line usr/bin/* which I assume sweeps up everything produced by the build under /usr/bin and puts it into the Debian package. Is there a way to exclude /usr/bin/comp from the machinekit-hal package so that we can install the machinekit-hal-dev package in multistrap systems? You can follow along with what I have been doing at cmcquinn/machinekit-hal <https://github.com/cmcquinn/machinekit-hal> and cmcquinn/machinekit-cnc <https://github.com/cmcquinn/machinekit-cnc>. Regards, Cameron McQuinn On Sunday, March 22, 2020 at 8:00:20 AM UTC-6, [email protected] wrote: > > Hi, > Mar 22, 2020, 03:09 by [email protected] <javascript:>: > > > What is the status of Travis CI builds for machinekit-cnc? I would love > to help get this going if needed. Let me know how I can help :) > > > The current status is that it is not working. And frankly have no idea if > it ever worked or was just left as a something from the original split into > separate repositories. I am currently trying to implement the CI/CD flow > based on Github Actions. (You can read about it here: > https://github.com/machinekit/machinekit-hal/issues/268 .) Main reason > for this is the higher limits for Open-Source project, it is simply in the > Github repository, so every fork will have it by default and Github will > store the artifacts for later download. > > Of course, if somebody will implement Travis CI jobs, then that's good for > redundancy. > > How I imagine it to work is following: The mk-cross-builder code was > integrated into Machinekit-HAL repository, so in given time some job will > build from it Debian images and store them in some repository (I am > thinking about Github Packages as it is directly connected to Github Git > repository and it is on one network with Github Actions workers). On this > will be constructed the Machinekit-HAL building and packaging. > > Given that Machinekit-CNC needs for its build the Machinekit-HAL (some > info can be glanced from > https://github.com/machinekit/machinekit-cnc/pull/93 ), I was thinking > that Machinekit-CNC will add another onion layer to the Machinekit-HAL > created builder images with its own build dependencies and from this get > its own builder (or builder which will be capable of building both > Machinekit-HAL and Machinekit-CNC). > > So what needs to be done is to rework the Debian packaging in > Machinekit-CNC ("debian" folder in root of the repository), build of the > specific Machinekit-CNC builder (so far it can just take the Machinekit-HAL > builder images from DockerHub) and the CI job. > > If you have specific question, just ask. Here or on the Matrix chat. > Cern. > > > > > Thanks, > > Cameron McQuinn > > > > -- > > website: http://www.machinekit.io blog: http://blog.machinekit.io > github: https://github.com/machinekit > > --- > > You received this message because you are subscribed to the Google > Groups "Machinekit" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] <javascript:>. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/machinekit/0bca17f7-2840-483a-9fc1-63b5a3e642fb%40googlegroups.com. > > > > > > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/d4a6d775-cb1c-4556-9cd2-807cbde080c7%40googlegroups.com.
