Some basic functions (some related to imaging) used by my projects.
- a compiler supporting C++20 (preferable Gcc >= 13, others may work as well, check source for "gcc","GNUC" )
- The build system was switched to meson
- The configure step is where needed dependencies will popup (so look for "Dependency ..." and see if the answer is "yes" if not install additional packages).
Use the following commands to get the prerequisits (run with sudo or as root):
apt-get install git build-essential automake libtool apt-get install libgtkmm-3.0-dev apt-get install libexif-dev apt-get install libjson-glib-dev
If you stick to an older gcc version e.g. < 13 (the major issue is the missing support for std::format) you may add:
apt-get install libfmt-dev
and check meson.build for "uncomment to use libfmt...". The header "psc_format.hpp" provides a switch between these format variants.
To build use from project dir use (the out of tree compile is preferred, in tree may work as well, but is not tested):
meson setup build -Dprefix=/usr -Dlog=YOUR_PREFERRED_LOGGING cd build meson compile
Using /usr is a suggestion, as other locations may require some lib/pkg/-path tweaking
for later steps to find this lib, so use it, unless you know what you are doing, as always ;)
Since the use of meson is not included for all the following projects they can still be build with autotools (those with configure.ac file in project dir):
autoreconf -fis mkdir build cd build ../configure --prefix=/usr make
For windows (get msys2 https://www.msys2.org/ ). Msys2 support multiple prefixes e.g. ucrt64 should be fine (see https://www.msys2.org/docs/package-naming/).
The names use variables to adapt to your favorite shell. But once you have selected a flavor you have to stick with it.
First install the prerequisits:
pacman -S base-devel
pacman -S ${MINGW_PACKAGE_PREFIX}-gcc
pacman -S ${MINGW_PACKAGE_PREFIX}-autotools
pacman -S ${MINGW_PACKAGE_PREFIX}-gtkmm3
pacman -S ${MINGW_PACKAGE_PREFIX}-libexif
Then it should be possible to clone&build the project:
meson setup build -Dprefix=${MINGW_PREFIX}
cd build
meson compile
I tried to adapt the following readme to use the
the ${MINGW...} environment, but if i missed one, replace
"mingw-w64-x86_64" with ${MINGW_PACKAGE_PREFIX}.
The lib requires to be installed before use so (on linux run as root):
meson install
If you don't like it (on linux run as root):
meson uninstall
The following may apply if you are not expecting to install this once.
The above method depends on using install and uninstall symmetrically.
To make this clearer say you misspell -Dprefix=/use (that's my favorite)
and make install will do whatever it was told and create /use.
You realize your mistake and correct the /use to /usr and install
into to correct location.
If you are attentive you may do a meson uninstall for the incorrect location,
if not the wrong files will sit there forever.
Another issue arises if you are a bit lazy leave out the make uninstall
on an update and just use make install. For most cases that will be fine...
But if with the upgrade a file should have been removed, it will stay in its
location and cause various issues e.g. an include-file in an unexpected location
may ruin your day.
My suggestion is to use a package manager for you operating system
(at least for linux this should not be too difficult).
As an example there is a PKGBUILD that works for me with Arch-Linux
(it uses a separate build directory, and is unmaintained).
Requires the extra step to install the package but avoids the issues mentioned above.
As an additional bonus, this will be sensitive to existing files ...
Now included is some basic logging support.
The default logging will be written to user home into the log directory.
If configured with:
-Dlog=sysd
systemd journal will be used as default log.
Query with e.g.:
journalctl SYSLOG_IDENTIFIER="glglobe"
The log is created with extended fields to see these use
-o verbose --output-fields=CODE_FILE,CODE_LINE,CODE_FUNC,MESSAGE.
As a alternative configure option:
-Dlog=sys
is supported to use syslog.
To change the log level the application config file e.g. ~/.config/glglobe.conf may support in main section e.g.:
logLevel=Info
For the Levels see Log.hpp at the moment Severe, Alert, Crit, Error, Warn, Notice, Info, Debug. But this is a work in progress so there might still be messages spilled on stdout...
- if you want to use LogView with syslog, as there is no universal syslog format you may need to adapt the LogViewSyslog::parse method
the structure of the libs used here is:
genericImg (used almost everywhere i think) + genericGlm | + monglmm | + picnic | + geodata | + glglobe + calcpp + nomad