libgphoto2 2.5.25 release

ptp2:
* Liveview support for Leica SL
* PTP 1.1 Streaming parameters added.
* Olympus OMD capture fixes
* Nikon DSLR/Z:
  * various improvements to liveview error reporting.
  * much more properties added, some values added
  * allow downloading of "large thumbnails" instead of "regular thumbnails",
    can be selected by "thumbsize" gphoto2 local setting.
  * fixes for D3000, D3100 methods
  * maximum capture wait extended to 1000 seconds (as the D870 has 900 seconds max now)
* Canon EOS
  * initialization fixes (if it breaks your EOS M or PowerShot, please report)
  * liveview enablement fixed
  * maximum capture wait extended to 90seconds
  * EOS R shutterspeed , aperture reporting fixed
* various bugfixes
* Cameras added to id list:
  * Sony NEX 5
  * Canon EOS 90D
  * Fuji XT-4
  * Sanyo VPC-FH1
  * Leica SL Typ 601

lumix:
* fixed initialisation, might help capture

all:
* ongoing stability fixes from AFL fuzzing

translation updates:
* sv

# libgphoto2

Hello and welcome to the wonderful world of gphoto! This is libgphoto2, the
successor of gphoto with lots of new features and additional camera
drivers.

If you miss a feature, would like to report success or failure, or have any
questions, please don't hesitate to contact our mailing list.


## What is libgphoto2?

libgphoto2 is a library that can be used by applications to access various
digital cameras.

For more information on gphoto, see [gphoto project home page].

There, you can also get information on mailing lists, supported cameras,
and availability of gphoto2. Another source of information is [gphoto github project page].

where you can access our SVN server to fetch the source code of
gphoto2, gtkam and GnoCam (see below).


## What is libgphoto2 not?

libgphoto2 itself is not a GUI application, opposed to gphoto. There are
GUI frontends for the gphoto2 library, however, such as gtkam for
example.

libgphoto2 can only talk to cameras the language of those it understands.
That is, if you own a camera that speaks a language that isn't published
anywhere and nobody has been able to figure out the meaning of the sentences,
libgphoto2 cannot communicate with those cameras.

Then, there are cameras supporting the so-called USB Mass Storage protocol.
This is a protocol that has been published and lets you access any storage
device, be it a camera or a disk connected via USB to your computer. As there
are already drivers for this protocol out there, you don't need an additional
library like libgphoto2. The list of camera that use USB Mass Storage is getting
longer everyday, so we won't publish it.

For a more up to date list, you can consult [camera list with support status].

Your operating system will tell you about that because it is likely to recognize
the device as a SCSI disk that you can mount (for Linux 'dmesg' will tell you).
Again, those cameras *cannot* be accessed through libgphoto2. Some of them can
be switched to use a different communication protocol and might be in that case
useable with libgphoto2.

Other camera support a protocol called PTP or USB Imaging Devices that has
been developed by Kodak and other. libgphoto2 does support PTP. Also working
will be cameras labeled as "PictBridge", which is a extension to PTP.

Almost all cameras that are not mass storage support it these days, including
but not limited to all Nikon, Canon, Fuji, Sony, Panasonic, HP and more.

PTP camera unknown to libgphoto2 will be detected as a generic PTP camera and
will work as-is without any changes.

MTP (Microsoft Transfer Protocol) capable devices will also be accessible,
since MTP is based on PTP.


## Platforms

libgphoto2 should compile and run on pretty much all Unix-like platforms.
libgphoto2 has _not_ (yet?) been ported to any operating system from MicroSoft.


## Bindings

- Java: [gphoto2-java](https://github.com/mvysny/gphoto2-java), [libgphoto2-jna](https://github.com/angryelectron/libgphoto2-jna)
- Python: [python-gphoto2](https://github.com/jim-easterbrook/python-gphoto2), [gphoto2-cffi](https://github.com/jbaiter/gphoto2-cffi)
- C#: [libgphoto2-sharp](https://github.com/gphoto/libgphoto2-sharp)
- Go: [go-gphoto2](https://github.com/aqiank/go-gphoto2)
- Rust: [gphoto-rs](https://github.com/dcuddeback/gphoto-rs)
- Node.js: [node-gphoto2](https://github.com/lwille/node-gphoto2)
- Ruby: [ffi-gphoto2](https://github.com/zaeleus/ffi-gphoto2)
- Crystal: [gphoto2.cr](https://github.com/sija/gphoto2.cr)


## How to set up libgphoto2

For information on how to set up libgphoto2 and its frontends, see
The gphoto2 Manual.

It is available at the following places:

 - At the gphoto website: [gphoto project home page]
 - In the SVN module gphoto2-manual

The gphoto2 Manual includes information about setting up USB
hotplugging.

If you run into problems, you may also consult the FAQ (also included
in The gphoto2 Manual).


## Frontends

gphoto2 is a command line frontend which is quite powerful,
especially in combination with scripts. See The gphoto2 Manual
for a short description.

For the GUI lovers, there are for example digikam (KDE), gthumb (GNOME),
f-spot (GNOME / Mono) and more. We also have a GTK2 reference GUI
called gtkam, which is unmaintained, its only special features are
capture ability.
Additionally, there are plugins for other programs available like
kio_camera (KDE - Konqueror) and a fuse plugin, gphotofs.


## Reporting Bugs

Every piece of software contains errors and flaws. So does
libgphoto2. When you encounter something that does not work, please do
the following:

1. Find out whether this is a known problem.

2. Reproduce the problem with debug output enabled and the language
    set to English, so that the development team will understand the
    messages. You can do this by running:

        env LC_ALL=C gtkam

    if you're using the gtkam frontend or running:

        env LC_ALL=C gphoto2 --debug-logfile=logfile.log --debug <options>

    using the gphoto2 command line interface.

3. Report the problem on the mailing list with the corresponding debug
    output if it is small. If it is more than a few kilobytes, please
    don't post the complete debug output on the list.

## Links

* [gphoto project home page](http://www.gphoto.org/)
* [gphoto github project page](https://github.com/gphoto)
* [gphoto camera list](http://gphoto.org/proj/libgphoto2/support.php)
* [gphoto camera remote control list and doc](http://gphoto.org/doc/remote/)
* [jphoto home page](http://jphoto.sourceforge.net/)
* [Information about using USB mass storage](http://www.linux-usb.org/USB-guide/x498.html)
* [gphoto development mailing list](mailto:gphoto-devel@lists.sourceforge.net)
* [gphoto user mailing list](mailto:gphoto-user@lists.sourceforge.net)
* [gphoto translation mailing list](mailto:gphoto-translation@lists.sourceforge.net)

========================================================================
libgphoto2 README.packaging
========================================================================

This file describes a number of things you should know when building
packages (.debs, .rpms, ports, emerges, etc. pp.)


========================================================================
libgphoto2 and libgphoto2_port
==============================

The libgphoto2 library builds on the libgphoto2_port library, which is
thus internally contained within every libgphoto2 release. By
installing libgphoto2, you always also install libgphoto2_port.


========================================================================
Installed files
===============

A standard install of libgphoto2 does about this:

   * The most important files:
     * ${libdir}/libgphoto2.{a,la,so}
     * ${libdir}/libgphoto2/<VERSION>/*.{a,la,so}        (camlibs)
     * ${libdir}/libgphoto2_port.{a,la,so}
     * ${libdir}/libgphoto2_port/<VERSION>/*.{a,la,so}   (iolibs)
     In most cases, you can remove the *.a and *.la files from the
     list of files to ship.
   * Packaging helpers:
     * ${utilsdir}/libgphoto2/print-camera-list
     * ${utilsdir}/libgphoto2/print-usb-usermap (linux-hotplug, obsolete)
     * ${udevscriptdir}/check-mtp-device
     * ${udevscriptdir}/check-ptp-camera
     Defaults: utilsdir=${libdir}, ${udevscriptdir}=${libdir}/udev.
     You probably want to ./configure udevscriptdir=/lib/udev and possibly
     utilsdir='${libexecdir}', depending on your system.
   * Documentation:
     * Man pages:
       * ${mandir}/man3/libgphoto2.3
       * ${mandir}/man3/libgphoto2_port.3
     * ${docdir}/camlibs/README.*    (camlib docs)
     * ${docdir}/{README,AUTHORS,NEWS}
     * ${docdir}/apidocs.html/       API docs
     * ${docdir}/{README,AUTHORS,NEWS}
     You may want to install these files into your custom locations.
     If you separate library from libfoo-devel packages, the former
     should probably ship with the camlib docs, and the general README
     and NEWS. Try configure --with-docdir=.
   * Translated strings:
     * ${datadir}/locale/*/LC_MESSAGES/libgphoto2-2.mo
     * ${datadir}/locale/*/LC_MESSAGES/libgphoto2_port-0.mo
     * ${datadir}/libgphoto2/<VERSION>/konica/*
       These files are required for the konica camlib to work at all.
   * For developers:
     * ${includedir}/gphoto2/gphoto2*.h
     * ${libdir}/pkgconfig/libgphoto2.pc
     * ${libdir}/pkgconfig/libgphoto2_port.pc

Note that utilsdir, udevscriptdir, etc. can be set at configure
time. See "configure --help".


========================================================================
Permission setup
================

We consider it a bug in the package if the package does not offer a
way for the user to just plug in his camera and use it. This may at
most require adding the user to a "camera" or "plugdev" group.

You will want to create HAL or UDEV rules by running this utility:

   * print-camera-list

This utility requires libgphoto2 and its camlibs being installed,
either

   * at package building time by doing a DESTDIR based temporary
     install somewhere and setting LD_LIBRARY_PATH and CAMLIBS before
     running print-camera-list
   * at package installation time as a post installation hook

The UDEV rules require two helper scripts/binaries, which obviously
need to be installed by the package:

   * check-mtp-device (not working yet)
   * check-ptp-camera

You can either use fixed permissions in the generated rules, or call
your own permission setup script to dynamically decide what to do.

(Contemporary example scripts are not being shipped yet.)


========================================================================
Development packages
====================

The recommended way to use libgphoto2 in a build process is to use
pkg-config and thus these files really should be shipped in a package:

   * /usr/lib/pkgconfig/libgphoto2.pc
   * /usr/lib/pkgconfig/libgphoto2_port.pc

We are still shipping

   * /usr/bin/gphoto2-config
   * /usr/bin/gphoto2-port-config

for compatibility reasons, but that will obviously break when you have
a /usr/lib64 vs. /usr/lib conflict. That problem is one the packager
will have to resolve - we consider this mechanism obsolete.


========================================================================
End of file.
========================================================================