After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 578027 - configure should fail hard when gphoto backend requested but cannot be enabled
configure should fail hard when gphoto backend requested but cannot be enabled
Status: RESOLVED FIXED
Product: gvfs
Classification: Core
Component: gphoto backend
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2009-04-05 14:24 UTC by Priit Laes (IRC: plaes)
Modified: 2012-04-30 10:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Make checks with --enable-gphoto2 stricter (1.02 KB, patch)
2009-05-04 17:33 UTC, Arun Raghavan
committed Details | Review

Description Priit Laes (IRC: plaes) 2009-04-05 14:24:05 UTC
Currently configure still succeeds when gphoto backend is requested but cannot be enabled.
Comment 1 Arun Raghavan 2009-05-04 17:33:58 UTC
Created attachment 133935 [details] [review]
Make checks with --enable-gphoto2 stricter

Attaching a patch to make the checks a little stricter. If --enable-gphoto2 is passed in but (a) libgphoto2 is not available, or (b) we can't use gphoto2 because we're not on Linux, the build errors out.

The automagic dependency calculation when no --enable-gphoto2 works just as it did before.
Comment 2 Pacho Ramos 2012-04-29 18:31:16 UTC
Can you finally commit this? Thanks a lot
Comment 3 Bastien Nocera 2012-04-30 10:17:59 UTC
(In reply to comment #2)
> Can you finally commit this? Thanks a lot

Would have been easier if it was in the correct format.
I also fixed the pkg-config checks surrounding this.


commit 7d0127ee181c0b282b8f99f461d26fce1c3a27b0
Author: Arun Raghavan <arun@accosted.net>
Date:   Mon Apr 30 11:15:49 2012 +0100

    build: Bail if gphoto support is requested but not available
    
    https://bugzilla.gnome.org/show_bug.cgi?id=578027