Right. Thanks for the pointer. Ran a quick test on some of the build profiles, and dockerfile-luw is missing dependencies for some of the linux builds, for example:
[exec] /bin/sh: 1: aarch64-linux-gnu-gcc: not found That should be an easy fix that I'm happy to do, but to the larger question of documenting the build process, I put the following to the community: 1. Do we want a docker file like dockerfile-luw, which provides an environment for the builds; or, 2. do we want a docker file like the one at https://github.com/aremily/commons-crypto that (nearly) completely automates a full build; or, 3. both; or 4. something else? I think there are benefits to 3, with the drawback being the potential confusion of having two dockerfiles in one project. I think, however, that clear documentation could mitigate that drawback, while providing a fully automated build capability as well as a flexible environment for targeted builds. Thoughts? On Thu, Jun 16, 2022 at 1:58 PM sebb <seb...@gmail.com> wrote: > On Thu, 16 Jun 2022 at 18:18, Alex Remily <alex.rem...@gmail.com> wrote: > > > > I just ran [2], and whatever it does, it doesn't appear to do a build of > > commons-crypto. > > That's correct; all it does is set up the environment. > You have to then run Maven in the container. > > > I'd appreciate it if any developers who have the time > > would take a look at the dockerfile here: > > > > https://github.com/aremily/commons-crypto > > > > If you're copying the dockerfile into your own fork, you'll need the > > makefile.common file as well. > > > > Alex > > > > On Thu, Jun 16, 2022 at 1:07 PM Jochen Wiedmann < > jochen.wiedm...@gmail.com> > > wrote: > > > > > On Thu, Jun 16, 2022 at 7:00 PM sebb <seb...@gmail.com> wrote: > > > > > > > [1] src/docker/Dockerfile > > > > [2] src/conf/Docker/Dockerfile-luw > > > > > > Have to admit, that I wasn't aware of [2], when I created [1]. Mine is > > > incomplete, and can easily be removed. Was basically just an attempt > > > to reproduce the build instructions in the hope, that others would > > > verify, and fix my errors. > > > > > > Jochen > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
