Increase verbosity for 'openage --version'

[simonsan]

We give the following information. Output (updated 04/05/2020):

openage v0.4.0-131-ga3d99602b [devmode]
inotify, opengl, ci-cfg NOT SET
GNU 7.5.0 [ -fdiagnostics-color=auto]

== Python ==
Python        3.6.9 (default, Nov  7 2019, 10:44:02)
[GCC 8.3.0]
Python C API  1013
Cython        0.26.1
Jinja2        2.10
NumPy         1.13.3
Pillow        5.1.0
Pygments      2.2.0

== C++ ==
Eigen         3.3.4
Harfbuzz      1.7.2
Qt            5.9.5
SDL-runtime   2.0.8
libc-compile  2.27
libc-runtime  2.27
nyan

Windows

openage v0.4.0-141-g20640dba [devmode]
opengl, ci-cfg NOT SET
MSVC 19.25.28614.0 [/DWIN32 /D_WINDOWS /W3 /GR /EHsc /MP]

== Python ==
Python        3.7.7 (tags/v3.7.7:d7c567b08f, Mar 10 2020, 10:41:24) [MSC v.1900 64 bit (AMD64)]
Python C API  1013
Cython        0.29.17
Jinja2        2.11.2
NumPy         1.18.3
Pillow        7.1.2
Pygments      2.6.1

== C++ ==
Eigen 3.3.7
Harfbuzz 2.5.3
OpenGL 4.4.0 - Build 21.20.16.4574
Opus unknown
Qt 5.12.8
SDL-runtime 2.0.12
libc-runtime Windows
nyan

For future debugging on the user side we could give more information:

• [x] libc
• [x] sdl-version
• [x] Qt-version
• [x] eigen
• [x] harfbuzz
• [x] version numbers of python determined during compile time
• [x] python packages version
• [x] numpy
• [x] python imaging library (PIL)
• [ ] OpenGL version number (create new context -> epoxy_gl_version() ?)
• [x] nyan version number
• [ ] opus(file) version (doesn't seem to give version output on win builds for now) - FIX needed
• [ ] embedded python version (packaging)

Open for discussion:

• [ ] cmake version
• [ ] libpng
• [ ] Freetype
• [ ] ZLIB
• [ ] PNG
• [ ] SDL2Image
• [ ] Opus (doesn't seem to give version output on win builds for now) - FIX needed
• [ ] Ogg

Optional:

• [ ] GCCBacktrace
• [ ] gperftools-profiler
• [ ] gperftools-tcmalloc
• [ ] ncurses
• [ ] vulkan

In addition: jj quote:

for all I care, the versions of every single thing that we have and that has a version.

For sure these all are information we can reuse when it comes to error reporting, #1172.

Categories We could sort them into sections for:

internal modules (converter, nyan-lib, etc.), (soon)
python section (interpreter, packages/modules)
c++ libraries and alike
_data format versions (like nyan file, asset/modpack version, etc.) (soon)

[Mese96]

As this is labelled as "good first issue", I would like to try it, as soon as I find some time this month. For a first time contributor, anything I need to know ? (Except reading contributing.md and getting the project to build)

[heinezen]

@Mese96 You should be good to go, it only involves fundamental Python knowledge :)

[Mese96]

Need to take a closer look where to get version numbers for OpenGL and libc

[simonsan]

If you have any questions feel free to ask us via IRC or Matrix. ;-)