summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Work around github workflow issue with presenting stderrHans Ulrich Niedermann2022-01-231-0/+1
|
* CI: build automake based example projectHans Ulrich Niedermann2022-01-238-2/+114
| | | | | | Add automake based example project using libgphoto2 to have the CI builds ensure that building a libgphoto2 frontend with this libgphoto2 is possible.
* pc files: Fix gphoto2 builds, avoid builds with wrong headersHans Ulrich Niedermann2022-01-223-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the *.pc files, use a C preprocessor include path both with and without the gphoto2/ path component: Cflags: -I${includedir} -I${includedir}/gphoto2 This allows both the preferred way to include gphoto2 headers #include <gphoto2/gphoto2.h> #include <gphoto2/gphoto2-camera.h> and also the early 2000s legacy way (still in use by kamera and others because we did not properly communicate and enforce that back when we were still stabilizing the API) #include <gphoto2.h> #include <gphoto2-camera.h> to produce builds with the libgphoto2 headers actually corresponding to the *.pc files in use. Any other option for the *.pc file Cflags either produces unintended build failures or builds which use the wrong header files (the `-I${includedir}/gphoto2` option), or breaks the `#include <...>` part of the libgphoto2 API from the early 2000s still in use by kamera and others (the `-I${includedir}` option). For details, see https://github.com/gphoto/libgphoto2/issues/717 and https://github.com/gphoto/libgphoto2/issues/717#issuecomment-1018040615 Fixes: https://github.com/gphoto/libgphoto2/issues/717
* pragma away the warnings for GNU style initializer designatorsHans Ulrich Niedermann2022-01-221-0/+6
| | | | | Use #pragma to allow GNU style range designators in the camlibs/pentax/js0n.c state machine table initializers.
* Allow clang compile with initializer overridesHans Ulrich Niedermann2022-01-221-0/+20
| | | | | | | | | | | | This catches clang in a clang specific C preprocessor conditional before clang gets a chance to mess up at pretending to be gcc. The camlibs/pentax/js0n.c state machine tables use a lot of both GNU style range designators [ a ... b ], and later overrides some of the values in the range. This is not very pure C, but relatively effient to code, so we can accept silencing some warnings here. Fixes: https://github.com/gphoto/libgphoto2/issues/761
* added hp photosmart e331Marcus Meissner2022-01-221-0/+2
|
* updated russianYuri Kozlov2022-01-221-146/+154
|
* added NULL ptr check to property caseMarcus Meissner2022-01-221-1/+1
|
* updated newsMarcus Meissner2022-01-211-0/+4
|
* free objectinfo only if we got and objectinfo (OK reply) , fixes ↵Marcus Meissner2022-01-191-2/+4
| | | | https://github.com/gphoto/gphoto2/issues/480
* add some safety measures to get configMarcus Meissner2022-01-181-2/+2
|
* Added PTP support for Panasonic BGH1Bart H. Plague2022-01-183-5/+472
|
* added nikon d6 as reportedMarcus Meissner2022-01-122-0/+5239
|
* added romanianMarcus Meissner2022-01-101-0/+1
|
* added new romanian translationRemus-Gabriel Chelu2022-01-101-0/+388
|
* added zv-e10 to default wait on startMarcus Meissner2022-01-101-0/+1
| | | | https://github.com/gphoto/gphoto2/issues/477
* merge a fix from mingw for ssize_t double definitionMarcus Meissner2022-01-101-0/+2
|
* configure: Allow --with-jpeg=yes argument againHans Ulrich Niedermann2022-01-101-23/+76
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Allow the --with-jpeg=yes configure argument again. This was broken by commit ea00220b6f44a00c2efa792c538f1804ebe183c2. The GP_LIBJPEG macro in the configure script now handles the following cases: --with-jpeg=no --without-jpeg Do not use libjpeg. Do not autodetect it either. --with-jpeg --with-jpeg=yes Autodetect libjpeg. If not found, abort. <no argument given> --with-jpeg=auto --with-jpeg=autodetect Autodetect libjpeg. If found, use it. However, it does *NOT* handle --with-jpeg=/path/to/somewhere at this time. Set LIBJPEG_CFLAGS and/or LIBJPEG_LIBS instead to specify which libjpeg to compile with and link against. This mostly matches the behaviour from before commit ea00220b6f44a00c2efa792c538f1804ebe183c2, which was --with-jpeg=no --without-jpeg Do not use libjpeg. Do not autodetect it either. --with-jpeg --with-jpeg=yes --with-jpeg=<any value other than "no"> Autodetect libjpeg. If found, use it. Otherwise, silently ignore the user's wish to build with libjpeg. <no argument given> Autodetect libjpeg. If found, use it. If someone is running configure with --with-jpeg=yes and libjpeg cannot be used, we can assume that building without using libjpeg is not the outcome the user expects. Fixes: https://github.com/gphoto/libgphoto2/issues/759 Closes: https://github.com/gphoto/libgphoto2/pull/760
* gitignore: add gp-gettext-setup.mk filesHans Ulrich Niedermann2022-01-101-0/+2
| | | | | | | Have git ignore the gp-gettext-setup.mk files which commit d18b440a72407fc371ec17a2a983976b813e5d97 added to the list of files being generated during builds.
* gitignore: Fix pattern for .vscode/ directoriesHans Ulrich Niedermann2022-01-101-2/+2
| | | | | | | | | | | | | | | | The vscode documentation[1] says that the editor use a directory named ".vscode", not "+.vscode". ".vscode" is also what the original commit[2] in pull request 100[3] contained. However, commit e9fafcd89d3e88767670800f684c58eee727b84f probably contained a cut and paste error and added the ignore pattern for directories called "+.vscode". [1]: https://code.visualstudio.com/docs/editor/workspaces [2]: https://github.com/gphoto/libgphoto2/pull/100/commits/d8ff05da8cf5c4790c6e8f0dd4dda34b382ec585 [3]: https://github.com/gphoto/libgphoto2/pull/100
* Fix lumix linking on mingwMiloš Komarčević2022-01-071-1/+1
|
* translation updatesMarcus Meissner2022-01-061-0/+2
|
* updated polishJakub Bogusz2022-01-062-3600/+4108
|
* updated ukrainianYuri Chornoivan2022-01-041-147/+155
|
* updated ukramniasnYuri Chornoivan2022-01-041-3454/+3984
|
* add notificaiton of rtanslation projectMarcus Meissner2022-01-031-0/+24
|
* switch to 2.5.28.1 developmentMarcus Meissner2022-01-032-1/+4
|
* 2.5.28 releasev2.5.28libgphoto2-2_5_28-releaseMarcus Meissner2022-01-032-3/+3
|
* keep canon eos remotemode=1 on exit, to keep the display onMarcus Meissner2022-01-032-1/+4
| | | | https://github.com/gphoto/gphoto2/issues/465
* added more NEWSMarcus Meissner2021-12-291-4/+9
|
* sync from libmtpMarcus Meissner2021-12-291-0/+12
|
* fix camera name, fixes https://github.com/gphoto/libgphoto2/issues/754Marcus Meissner2021-12-271-1/+1
|
* adjust hex id to have 4 digits, fixes ↵Marcus Meissner2021-12-201-1/+1
| | | | https://github.com/gphoto/libgphoto2/issues/753
* Verbose gettext domain consistency checksHans Ulrich Niedermann2021-12-161-2/+14
| | | | | Make the gettext domain consistency checks more verbose to help debugging https://github.com/gphoto/libgphoto2/issues/751.
* Add test-i18n.c i18n test programHans Ulrich Niedermann2021-12-122-0/+107
|
* Add pull-translations targetHans Ulrich Niedermann2021-12-123-1/+19
| | | | | | | Add pull-translations target to make it easier to pull translations from the Translation Project: make pull-translations
* Require gettext >= 0.18.3; remove GP_GETTEXT_HACKHans Ulrich Niedermann2021-12-1010-99/+240
| | | | | | | | | | | | | | | | | | | | | | | | This requires gettext version 0.18.3 or later, and it removes the GP_GETTEXT_HACK which used to generate a po/Makevars file from the po/Makevers.template. gettext 0.18.3 is the same gettext version requirement as libexif uses. gettext 0.18.3 has been released 2013-07-07, which is a similar timeframe of the autoconf, automake and libtool releases we require. If you ever need to build a post 2021 libgphoto2 from git on a system with pre 0.18.3 gettext, you can can always prepare a tarball using "make dist" on a system with gettext 0.18.3 or later, and build that tarball on the older machine. Not generating the po/Makevars file any more means that we need additional consistency checks for the parts of po/Makevars which cannot be derived from the Autoconf standard set of AC_SUBST()ed Makefile.in variables.
* Add Nikon Zfc supportOle Dalgaard2021-12-092-0/+2
|
* RELEASE-HOWTO.md: Improve markdown readabilityHans Ulrich Niedermann2021-12-091-42/+43
| | | | | Improve markdown readability, both as text and rendered as HTML.
* Document translating languages outside Translation ProjectHans Ulrich Niedermann2021-12-092-1/+9
| | | | | | Document translating languages outside Translation Project, as we are maintaining the German ("de") translation by ourselves.
* MAINTAINERS: remove rpm buildsHans Ulrich Niedermann2021-12-091-3/+0
| | | | | Remove rpm builds from the MAINTAINERS file, as we have already removed the rpm builds in commit 69b3fc54bc6533c8716af8c9d5ab7945fe7923dd.
* Add TODO comment about possibly using gettext's gettext.hHans Ulrich Niedermann2021-12-092-0/+12
|
* Remove commented out hack for pre-2001 gettextHans Ulrich Niedermann2021-12-091-8/+0
| | | | | Remove the commented out hack needed for pre-2001 gettext-0.10.35 and earlier.
* remove dup k1Marcus Meissner2021-12-081-6/+0
|
* added Sony ILCE-7RM4A https://github.com/gphoto/libgphoto2/issues/749Marcus Meissner2021-12-082-1/+1472
|
* added pentax k1 idMarcus Meissner2021-12-061-0/+2
|
* aded sony sx-hx80Marcus Meissner2021-12-061-0/+3
|
* added pentax k1Marcus Meissner2021-12-061-0/+6
| | | | https://github.com/gphoto/gphoto2/issues/469
* added pentax k1Marcus Meissner2021-12-061-0/+6
|
* ptp2: add Canon IXUS 132Wolfram Sang2021-12-032-0/+293
|
View Lorry Controller Status