Most of the examples give wrong impression that `GP_UNKNOWN_EVENT` data does not need to be freed / is not heap allocated, however it's not the case - those messages are always `malloc`'d by corresponding drivers.
We probably do not need to dist-upgrade (or upgrade), and dist-upgrade
can take a long time on the github runners.
We only had this while trying to work out how to work around the
libgd-dev dependency issue, so we can remove the dist-upgrade step.
Work around libgd-dev dependency issue apparently caused by a 3rd party
repository with PHP and nginx and related stuff like libgd.
So we remove nginx and libgd3 to get rid of the relevant 3rd party
packages which pull in their libgd, and only then install libgd-dev
which then comes from Ubuntu proper and works.
As we need neither nginx nor php, this should work for libgphoto2.
This appears to be a reoccuring problem on github runners, so keeping
this workaround in place looks like the way to go for the future.
See also https://github.com/actions/runner-images/issues/6153
and recursively follow the linked issues and comments for more
information.
Consistently use the same notation and formatting for all
camlib Makefile-files, which uses
* common $(camlib_cflags)
* common $(camlib_cppflags)
* common $(camlib_dependencies)
* common $(camlib_ldflags)
* common $(camlib_libadd)
and then groups additional related definitions together,
making it obvious when e.g. bar_la_LIBADD adds FOO_LIBS
but bar_la_CPPFLAGS forgot to add FOO_CFLAGS.
Commit e47c13fd8e updates the
libgphoto2_port version from 0.12.0 to 0.12.1, but fails to
update libgphoto2_port/NEWS accordingly.
This updates libgphoto2_port/NEWS with the 0.12.1 version number,
thus fixing the "make distcheck" target's part checking NEWS.
Change the libgphoto2_port version from 0.12.0 to 0.12.1 so that
the libgphoto2 pkgconfig files can require libgphoto2_port >= 0.12.1
due to new symbols added.
This will not catch all possible build/install/link messups, but
will not hurt anyone and could catch some messups.