summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Update the checks for libjpeg (GP_LIBJPEG)Hans Ulrich Niedermann2021-11-037-22/+152
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Update the checks for libjpeg to try libjpeg.pc with PKG_CHECK_MODULES first, and also to allow explicitly set LIBJPEG_CFLAGS and LIBJPEG_LIBS. The old detection logic did not allow specifying the location of libjpeg at all. It only allowed either disabling libjpeg or using libjpeg from the default include and linker paths. So this also changes the places in the Makefiles where we used to add @LIBJPEG@ to the linker to both link with $(LIBJPEG_LIBS) and compile with $(LIBJPEG_CFLAGS). The new configure logic keeps --without-jpeg to force- disable libjpeg, but updates the detection of libjpeg to first try the LIBJPEG_* variables if given, otherwise try PKG_CHECK_MODULES for libjpeg, and only then falls back to the old way of just trying the default include and link locations for libjpeg. This mentions more information in the configure summary if not building with libjpeg. This is the first time we make it possible to build with libjpeg from e.g. FreeBSD ports' or MacOS homebrew's jpeg-turbo packages.
* Update libltdl checks (GP_LIBLTDL)Hans Ulrich Niedermann2021-11-034-84/+216
| | | | | | | | | | We still do not use LTDL_INIT() as LTDL_INIT insists on us shipping libltdl sources in our release tarballs and we still do not like shipping third party sources. This now checks locations other than the default include and linker paths, so that configure should find libltdl by itself now on e.g. FreeBSD or OSX/homebrew.
* Make the compiler warnings work with clang, gcc, and othersHans Ulrich Niedermann2021-11-032-20/+159
| | | | | | | | | | | | | | | | | | | | | | Make the compiler warnings work with clang in addition to gcc by test compiling all warning options before actually using them. This came up when the pedantic build tests failed on FreeBSD 13. To achieve this, we add -Werror=unknown-warning-option to the CFLAGS for clang to abort immediately on encountering an unknown warning option. This means we now only add warnings which the compiler (clang, gcc, or whatever) actually supports. As running configure now checks whether compiling is possible for each warning flag, this should not introduce compatibility issues where builds which used to work now fail to build. However, you can always opt to not use the generated CFLAGS by setting CFLAGS to empty or whatever else you want when running your build, e.g. like make all check CFLAGS=
* tests: add pedantic compile tests for -std={c2x,c++20}Hans Ulrich Niedermann2021-11-032-0/+26
| | | | | | | | Add a pedantic C compile test for c2x in addition to the existing ones for c90, c99, and c11. Add a pedantic C++ compile test for c++20 in addition to the existing ones for c++98, c++11, c++14, and c++17.
* tests: Always define, but only test conditionallyHans Ulrich Niedermann2021-11-031-19/+18
| | | | | | | Always define the test programs, but only conditionally test them. This makes certain that they can be build, that the sources are added to the dist tarball, etc.
* tests: Remove old pedantic compilation testsHans Ulrich Niedermann2021-11-031-51/+1
| | | | | | | | | | | | These did not work with C++ on FreeBSD 13 anyway, due to c++98 not working there, which the old pedantic compilation just assumed was working without testing it in configure. The new pedantic compilation tests offer a multitude of language standards including c++98, but only tries building the pedantic compilation tests for those language standards for which configure has shown that building programs is possible at all.
* gp-camlibs.m4: Fix GP_SLEEP invocation in in Gentoo hackHans Ulrich Niedermann2021-11-032-117/+437
| | | | | | | | Fix the GP_SLEEP invocation in the Gentoo hack warning which adds the ptp2 camlib if the only camlib requested is canon, as modern Canon cameras use the ptp2 camlib, not the canon camlib. Also syncs gphoto-m4/gp-camlibs.m4 to libgphoto2-port/gphoto-m4/.
* HACKING.md: Add note about printf(3) fmt strings using "%m"Hans Ulrich Niedermann2021-11-031-0/+5
| | | | | | The printf(3) format string character "%m" is available on Linux/glibc and FreeBSD, but not on MacOSX. So using "%m" should be limited to system specific code.
* simplified after prohibit simplificationMarcus Meissner2021-10-311-112/+172
|
* avoid duplicate mvoie / liveview prohibition code strings for translationMarcus Meissner2021-10-312-29/+29
|
* HACKING.md: Update with C99 being our requirementHans Ulrich Niedermann2021-10-311-8/+9
| | | | | | | We have been requiring at least parts of C99 like stdint.h for some time now, but HACKING.md has not reflected that until now. Closes: https://github.com/gphoto/libgphoto2/issues/724
* HACKING.md: Misc small improvements (grammar, whitespace, etc.)Hans Ulrich Niedermann2021-10-311-8/+8
|
* more spellcheckingMarcus Meissner2021-10-301-43/+43
|
* more speling fixesMarcus Meissner2021-10-291-24/+24
|
* spelling fixesMarcus Meissner2021-10-291-16/+17
|
* german translation completedMarcus Meissner2021-10-291-208/+178
|
* updated germanMarcus Meissner2021-10-281-401/+250
|
* make update-poMarcus Meissner2021-10-281-2831/+3232
|
* sync gp-gettext-hack.m4 files between gphoto-m4 dirsHans Ulrich Niedermann2021-10-261-6/+9
|
* tests: declare local variable localHans Ulrich Niedermann2021-10-262-0/+2
| | | | | | | Declare local variable local by declaring it static. This avoids the clang warning about the variable not being declared static.
* tests: include system headers before gphoto2 headersHans Ulrich Niedermann2021-10-262-4/+4
| | | | | In the pedantic compilation tests, include the system headers before gphoto2 headers - which should be the way to do things.
* POTFILES.in: Add remaining source files using i18n.hHans Ulrich Niedermann2021-10-253-2/+16
| | | | | | | Add remaining source files including libgphoto2/i18n.h or libgphoto2_port/i18n.h to the respective POTFILES.in, regardless of whether or not the source file actually contains translated strings.
* POTFILES.in: Add ptpip, vusb iolibsHans Ulrich Niedermann2021-10-251-2/+5
| | | | | | | All three added sourcefiles had the i18n headers, but strings actually marked for translations are only found in ptpip/ptpip.c, not in any of the vusb/vcamera.c or vusb/vusb.c files.
* Rename libgphoto2_port test directory testsHans Ulrich Niedermann2021-10-257-3/+8
| | | | | Rename the libgphoto2_port/test directory to libgphoto2_port/tests to make its name the same as libgphoto2/tests.
* examples: Force #include beginning with "libgphoto2/"Hans Ulrich Niedermann2021-10-251-1/+1
|
* library versioning comment without trailing spacesHans Ulrich Niedermann2021-10-252-8/+8
|
* Delete old debug commentsHans Ulrich Niedermann2021-10-251-2/+0
| | | | Delete some old debug comments from the configure script.
* Factor out i18n stuff into separate i18n.h filesHans Ulrich Niedermann2021-10-25110-1641/+309
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* sync gp-check-library.m4 between gphoto-m4 dirsHans Ulrich Niedermann2021-10-254-44/+15
| | | | | | | | | | | 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.
* Here document: Use <<EOF everywhereHans Ulrich Niedermann2021-10-252-11/+10
| | | | | | | | 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.
* tp6081-dump: include <unistd.h> for close(2), add more staticHans Ulrich Niedermann2021-10-251-0/+6
|
* example: include <unistd.h> for close(2), unlink(2), getpid(2)Hans Ulrich Niedermann2021-10-251-0/+2
|
* Typo fix: It is _SOURCES, not _SOURCEHans Ulrich Niedermann2021-10-242-3/+3
|
* add more newsMarcus Meissner2021-10-231-4/+20
|
* NEWS: converted text from iso to utf-8, removed linux-hotplugHans Ulrich Niedermann2021-10-221-0/+2
|
* added note for the 1:0:7 revMarcus Meissner2021-10-221-0/+1
|
* rev the age of the library.Marcus Meissner2021-10-221-2/+3
| | | | see https://github.com/gphoto/libgphoto2/pull/738
* ptp2: Reload object info on PTP_CANON_EOS_CHANGES_TYPE_OBJECTINFO_CHANGEDavid Rosca2021-10-221-0/+5
|
* filesys: Add gp_filesystem_set_info_dirtyDavid Rosca2021-10-224-0/+36
| | | | Use it in ptp2 PTP_EC_ObjectInfoChanged.
* somre more updatesMarcus Meissner2021-10-211-2658/+3915
|
* some updatesMarcus Meissner2021-10-211-79/+38
|
* Update libphoto2_port/po/de.po to UTF-8 after allHans Ulrich Niedermann2021-10-211-69/+69
| | | | | | | | | | | As the German translation ("de") is configured as "external" at the Translation Project, there will be no updated `de.po` files from the Translation Project to overwrite what we have in our source tree. So the gphoto project needs to maintain the de.po file independent from the Translation Project, and updating the file from ISO-8859-1 to UTF-8 is a part of that.
* emit a FILE CHANGED event if the ObjectInfo changes.Marcus Meissner2021-10-201-0/+43
| | | | e.g. if you select "protect" on the camera.
* Remove linux-hotplug supportHans Ulrich Niedermann2021-10-199-306/+1
| | | | | | | | | | | | | | The linux-hotplug mechanism has been replaced by udev and hwdb for quite some time now, so we can remove the support for packaging libgphoto2 with linux-hotplug. For a rough idea of the timeline of linux-hotplug being replaced, the last release of hotplug appears to have been in March of 2004: https://sourceforge.net/projects/linux-hotplug/files/ and the Fedora 5 (released March 20, 2006) release notes mention the hotplug package having been removed.
* Remove unused code adding x bit to *.shHans Ulrich Niedermann2021-10-191-10/+0
| | | | | | There are no *.sh files being generated by AC_CONFIG_FILES, so the code bit setting the executable bit on *.sh is not needed.
* Remove rpm packagingHans Ulrich Niedermann2021-10-1910-503/+5
| | | | | | | | | | 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.
* Use && and || instead of test arguments -a and -oHans Ulrich Niedermann2021-10-194-5/+5
| | | | | For portability, use && and || instead of the test arguments -a and -o.
* Sync gp-byteorder.m4, supporting 64bit valuesHans Ulrich Niedermann2021-10-191-0/+4
|
* Remove unused remnants of convenience libltdlHans Ulrich Niedermann2021-10-195-126/+0
| | | | | | Not that its presence hurt anything, but we could have removed the libltdlc.la stuff some time in the 2000s.
* only ovbrwrite the PEF header for the K100D.Marcus Meissner2021-10-171-21/+23
| | | | see https://github.com/gphoto/gphoto2/issues/459
View Lorry Controller Status