Revisions to the dockerfile

[rpgoldman]

There are some issues with the existing Dockerfile. I have added a new one (not preceded by a .) trying to fix it.

So far:

1. Added more apt package installations, which seem necessary.
2. Fix the download location for CoCoA. Fixes Link for CoCoA lib download needs update #50

Right now, this does not work. CoCoA does not build correctly. It seems not to find dependencies that are installed.

[rpgoldman]

I have fixed the CoCoA build problems, which was due to a bug in CoCoA's script for finding the boost libraries: it made assumptions about how boost is installed that are not true, at least on Ubuntu.

Unfortunately, even after the fix, the resulting Docker image does not appear to install CoCoA headers. See smtrat issue 97

I don't know much about cmake, but I wonder if it would make more sense to build and install CoCoA more directly, rather than having cmake do it? The cmake script for installation has to have URLs hard-coded in it, and makes it hard to control CoCoA's configuration. I don't know how this works for a conventional install, but for building a Docker image, at least, it might be nicer to install CoCoA first, using CoCoA's own installation process, and then building carl afterwards. (But in that case, I do not know how one would make the Carl build process find the CoCoA installation.)

[rpgoldman]

In order to move this past draft status, I need some advice on

1. revising the git configuration https://github.com/rpgoldman/carl/blob/487b3f3ff05667509412fecfeaf256dc771f7bb3/Dockerfile#L18-L19 and
2. how to make the location of the boost libraries vary according to the host architecture https://github.com/rpgoldman/carl/blob/487b3f3ff05667509412fecfeaf256dc771f7bb3/Dockerfile#L30

[rpgoldman]

This needs refinement, but it fixes multiple problems with building Carl.

[rpgoldman]

This needs refinement, but it fixes multiple problems with building Carl.