C M4 Makefile Perl Python Shell Other
Failed to load latest commit information.
camlibs added EOS Rebel T7i Aug 6, 2017
doc removed baudboy.h usage Oct 22, 2011
examples also log the domain Jul 31, 2017
gphoto-m4 synchronize gphoto-m4 files Jul 20, 2017
gphoto2 clarify wait_for_event documentation a bit Apr 25, 2016
libgphoto2 added a note that gp_file_new_from_fd takes over ownership of the fil… Aug 10, 2017
libgphoto2_port Add list of IOLIBs to configure summary Aug 2, 2017
packaging scripts: remove bashisms. Jan 24, 2017
po updated swedish May 21, 2017
tests add log_remove func too Jun 3, 2017
.gitignore added missing example binaries to .gitignore Dec 5, 2016
.travis-translate-pkgs translate gettext to gettext May 8, 2017
.travis.yml newest travis images seemd to need gettext May 8, 2017
AUTHORS merge over the rest of AUTHORS list addtions from svn Aug 2, 2015
COPYING replace (c) and (C) by � Dec 15, 2002
ChangeLog Eliminated some compiler warnings, fixing a couple of small Jul 11, 2010
HACKING fix selective install instructions Sep 3, 2007
INSTALL SVN is not used at all anymore. Jul 22, 2017
MAINTAINERS updated to current state May 27, 2013
Makefile.am added gphoto-m4 to SUBDIRS for make dist Oct 17, 2015
NEWS switch to devel Jun 5, 2017
README.in updated regarding ptp Jul 10, 2012
README.packaging Fixed minor file name typo Nov 1, 2010
TESTERS * TESTERS: add myself as tester for Canon 20D Oct 18, 2004
configure.ac switch to devel Jun 5, 2017
coverity-model.c From: Axel Waggershauser <awagger@web.de> Sep 9, 2014
gphoto2-config.in Consistently use #include <gphoto2/gphoto2-foo.h> everywhere. Sep 28, 2006
installcheck.mk INSTALLCHECK_DEPS: additional dependencies for installcheck target Dec 11, 2006
libgphoto2-uninstalled.pc.in Consistently define driverdir in all *.pc files Jul 18, 2017
libgphoto2.pc.in Avoid overlinking of libexif Jan 14, 2016



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

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


There, you can also get information on mailing lists, supported cameras,
and availability of gphoto2. Another source of information is


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

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 


Your operating system will tell you about that because it is likely to recognise
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 developped 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.


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

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: @URL_GPHOTO_HOME@

 - In the SVN module gphoto2-manual

The gPhoto2 Manual includes information about setting up USB

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


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 abilitiy.
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.