Add Ubuntu compil command

[flodef]

Add Ubuntu compil command on a specific line, guided by many comments. Should be clearer and faster.

[OzFalcon]

I don't see what packages this shows that are not already listed in the Linux/Required/Optional libraries/packages.

[flodef]

I just added some command prompt to help newbies like me compile under Linux.
I spend time to find those, so I thought that it was better to already have it than to search everytime someone wants to compile.

[merwok]

Maybe the proposed change here duplicates available info, but that info is not as friendly as it could be:

Install the following development libraries on your system:

[...]
    FreeType 2
    The following FFmpeg libraries (required for videos):
        avformat,
[...]
        OpenGL and GLU (or OpenGLES for GLES version)
    JPEG library
    Make and Package Config

People have to read that and translate it to package names like libfreetype6-dev (2 → 6, don’t forget -dev), libavformat58-dev (ffmpeg is not in the name), something for opengl + glu or opengles (+ glu too? not clear), libjpeg-dev or is libjpeg62-turbo-dev ok, make and pkg-config (first time I see it spelled out Package Config 🙂)

So I think the PR author has a point, even if the proposed change is the wrong location.
Maybe adding the package names in the list (that I quoted), or just after, could help.
One objection is that these names only work for debian-ubuntu-etc, and the numbers will change: you could write libavformat*-dev for the second issue, and give both debian and rpm-style names for the first issue.

Just an outsider perspective, hope this helps!

[flodef]

@merwok Thank you so much for this detailed message. That was exactly the purpose of this commit.
So yes, it helps a lot.

[OzFalcon]

While it is helpful to have a more friendly text for package names and or compile instructions, it can cause confusion when said package names change both across distributions and across distribution releases.
Regarding Ubuntu specific packages/instructions, This would be more suited for Debian packages/instructions in that Debian is the base of many other derivatives. Then only minor changes for said derivatives would need be noted.

However, Given all the above - I Don't think this is the direction the author has in mind.
It appears from recent revisions to this text that a simpler less cluttered approach is the aim.

As an outside to this, The "attract/debian/control" file does indeed list the required packages which I suspect would be the same for most if not all Debian based derivatives. In fact you should be able to make installable packages under Ubuntu with it.
Quote:

A debian package may be built using either dpkg-buildpackage or sbuild using the existing source/debian folder.
dpkg-buildpackage can be used on the target system, sbuild is useful when building for an alternate release.
Provided all dependncies are met then run dpkg-buildpackage from a terminal in the source folder.

	dpkg-buildpackage --sanitize-env --no-sign -b -rfakeroot

If you are compiling for a different release of Debian (eg. Target = Debian 10, Compiling on Debian 11) then
you will need to setup an environment for sbuild. See https://wiki.debian.org/sbuild
Then run sbuild from a terminal in the source folder.

	sbuild -d buster