Re: Partial support, unreleased builds, path to full support

Hi,

On Fri, Jan 10, 2025 at 10:59:46AM -0500, Sam Friedman wrote:
> Hey all,
> 
> I have a slightly generalized set of questions:
> 
> 1) What is the path by which a camera gets full support?

There is camera classes, which Canon EOS is one part.

If the camera belongs to such a class, it will work even without having the USB Id specified directly.

There are some small pieces added for the R100, but it largely should work.

> 2) How do I install a libgphoto2 version that isn't a released version?

Either you can do yourself:

git clone  https://github.com/gphoto/libgphoto2/
autoreconf -i -f 
./configure --prefix=/usr/ --libdir=
make
sudo make install

or on Debian like systems there is a tool doing mostly the same:
https://github.com/gonzalo/gphoto2-updater

> 3) If I have a libgphoto2 version running locally that supports my camera,
> how do I ensure python-gphoto2 is binded to the specific version of
> libgphoto2?

See Jims mail.

> As an example (and the one relevant to my needs):
> The Canon R100 seems to be supported in libgphoto2 version 2.5.31.1
> <https://github.com/gphoto/libgphoto2/issues/924>. However, reading user
> jensanjo's output in `summary.txt`, makes it sound like the camera doesn't
> actually support image capture, just file downloading.

it lists:

        No Image Capture, No Open Capture, Canon EOS Capture, Canon EOS Capture 2

Meaning it supports EOS Capture.

> The R100 is not listed on the gphoto2 site's list of supported cameras
> <http://gphoto.org/proj/libgphoto2/support.php>.

This will happen once I find time to do a 2.5.32 release.

> So I'm curious how I can go from my current state which is having the
> released version of gphoto2, libgphoto2, and python-gphoto2 on my system,
> to 1) having a system that can run the R100 at presently-supported levels,
> and then 2) at full-support levels.

Ciao, Marcus