The docker script I posted is used to create a docker image using the docker build command. This loads an existing image (in this case sl == Scientific Linux) and then installs software we need etc.. I decided to "build" the docker image including FLTK downloaded and compiled/built. The result is a docker image I can run and thus use similar to a VM but it's a different technology. Once built it's saved on the local system for reuse. I could run new FLTK builds by starting a docker container using the existing image and running only git pull and make because everything is preinstalled.

The CI builds on GitHub and GitLab are similar pre-configured docker containers which we're using to build the software, mostly based on Ubuntu IIRC, but also macOS and Windows. Installing necessary packages is common to both approaches, hence it's very similar.

My intention to use docker in the first place (some weeks ago) was to be able to use different Linux distros and try to build FLTK so I can find out which package installers to use and which packages need to be installed. The goal is to help users and/or document builds on different systems. You can use even much older Linux systems for testing.

In this case I just wanted to be able to reproduce the error with "your" Sci Linux system to be able to test myself whether symbol prefixing can fix this error w/o installing a full VM. Building a docker image is done in minutes.

My next step will be testing symbol prefixing. Tomorrow. Hopefully.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.