| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Factor out the i18n definitions into i18n.h include files:
One include file each for libgphoto2 and for libgphoto2_port.
This removes the complete
#ifdef ENABLE_NLS
# include <libintl.h>
# undef _
# define _(String) dgettext (GETTEXT_PACKAGE, String)
# ifdef gettext_noop
# define N_(String) gettext_noop (String)
# else
# define N_(String) (String)
# endif
#else
# define _(String) (String)
# define N_(String) (String)
#endif
block (which in some occasions defines even more macros)
and replaces it with a single line
#include "libgphoto2/i18n.h"
for camlibs and libgphoto2 itself and with
#include "libgphoto2_port/i18n.h"
for iolibs and libgphoto2_port itself.
This gives us two central locations to change the defintions.
|
|
|
|
|
|
|
|
|
|
|
| |
The gphoto-m4 gp-check-library.m4 has been using PKG_PROG_PKG_CONFIG
since commit c1ab67b7288359066b4884d3058e712f6170da35 (2017-08-29),
so this makes the libgphoto2_port/gphoto-m4 use the same code.
As PKG_PROG_PKG_CONFIG provided by pkg-config's pkg.po, this means
we now require that to be present - and we should better check at
autoreconf time that the PKG_PROG_PKG_CONFIG macro is actually
defined.
|
|
|
|
|
|
|
|
| |
Using EOF does the job, is well readable, and there is
just no reason to use any other string.
On the contrary, it may cause additional trouble when
using m4_pattern_forbid.
|
|
|
|
|
|
|
|
|
|
| |
While adding support for "make rpm" appeared to be a good idea in the
early 2000s, it really is not and only clutters up the build system.
At least the libgphoto2_port translation cannot have worked in the
rpm package since at least 5255d802102c10f971dc98f10828451d9922340d
from 2007-10-28, so it is a good guess that this has not really been
in use.
|
|
|
|
|
| |
For portability, use && and || instead of the test arguments
-a and -o.
|
|
|
|
|
|
| |
Not that its presence hurt anything, but we could
have removed the libltdlc.la stuff some time in
the 2000s.
|
|
|
|
|
|
|
|
| |
Fix the output configure prints about DEFAULT_CAMLIBS
and DEFAULT_IOLIBS.
This only affects the output configure prints, no
actual config changes are happening.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This improves the definition of the camlib and iolib compile time
install location and the runtime lookup location to use the same
mechanism of using variables.
Example uses for Windows builds using the default install
location:
./configure \
DEFAULT_CAMLIBS='./libgphoto2' \
DEFAULT_IOLIBS='./libgphoto2_port'
Or example use for explicitly defining the install location
as well:
./configure \
camlibdir='/path/to/camlibs' \
DEFAULT_CAMLIBS='./libgphoto2' \
iolibdir='/path/to/iolibs' \
DEFAULT_IOLIBS='./libgphoto2_port'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make CAMLIBS and IOLIBS fallback locations (where libgphoto2 looks for
camlibs at runtime if the CAMLIBS environment variable is not set, and
where libgphoto2_port looks for iolibs at runtime if the IOLIBS
environment variable is not set) configurable at configure time.
The runtime lookup location DEFAULT_CAMLIBS and DEFAULT_IOLIBS can be
set independently from the installation location camlibdir and iolibdir.
This is to accommodate systems like Windows where it apparently makes
sense to install files to a location at build time which is different
to where the files will eventually end up being used from:
./configure \
--with-camlibdir='/path/to/camlibs' \
DEFAULT_CAMLIBS='./libgphoto2' \
--with-iolibdir='/path/to/camlibs' \
DEFAULT_IOLIBS='./libgphoto2_port'
As this interface is a bit ugly mixing the variables with the
--with-argument, we will improve that in the next commit.
|
|
|
|
|
| |
Use a common m4 macro GP_DRIVERDIR for defining iolibdir and IOLIBS
in libgphoto2_port and camlibdir and CAMLIBS in libgphoto2.
|
|
|
|
|
| |
I have no idea how that non-ASCII hyphen character made its
way into that m4 file, but this returns a simple ASCII character.
|
|
|
|
| |
See https://github.com/gphoto/libgphoto2-python/issues/4
|
|
|
| |
stdint.h has wide adoption at this point, so it should be safe to use.
|
|
|
|
| |
options
|
| |
|
|
|
|
| |
fixes https://github.com/gphoto/libgphoto2/issues/475
|
| |
|
|
|
|
| |
Fixes: 6f65d24796a0aaca0c20f4c074aa71e39f38e68d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Check that programs including libgphoto2 headers compile
when compiled for a number of different language standards:
C: ansi c99 c11
C++: ansi c++98 c++11 c++14 c++17
For each of these language standards, if the compiler does not
compile an empty example program, we do not test whether compiling
with the gphoto2/*.h headers included works.
This will work with GCC as the compiler, and also should work with
CLANG as the compiler as CLANG is mostly compatible in these matters.
On other compilers, the test compile of the empty program should
fail, and thus no checks with the gphoto2/*.h headers included will
be performed.
C90/ANSI C apparently does not define __STDC_VERSION__, so the
C source code needed to be changed to become ANSI C compatible.
In C++ pedantic compilation source, we now use actual C++ code
instead of relying on C code working when compiled as C++ code.
In Travis CI, we now actually require both C and C++.
|
|
|
|
|
|
|
|
|
| |
Allow setting SLEEP=no to disable sleep on warnings like
../configure SLEEP=no --prefix=/foo/bar ...
This is implemented with GP_SLEEP and gp_sleep similar to
m4sh's AS_ECHO and $as_echo.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This uses proper set operations both for GP_CAMLIB and for handling
the --with-camlibs value. This allows all GP_CAMLIB definitions to
be present at autoreconf time (as m4 code) time while some camlib
definitions being conditional at the time of the configure run (in
the sh code).
The ./configure output is still a bit verbose, but we can reduce that
verbosity later when we have found out that this works well on people's
different systems.
Fixes: https://github.com/gphoto/libgphoto2/issues/467
|
| |
|
|
|
|
| |
Tag a lot of camlibs as obsolete / outdated
|
|
|
|
| |
fixes https://github.com/gphoto/libgphoto2/issues/244
|
| |
|
| |
|
| |
|
| |
|
|
|