Skip to content

More hydra gtk#1047

Merged
vanhauser-thc merged 10 commits intovanhauser-thc:masterfrom
elboulangero:more-hydra-gtk
Nov 22, 2025
Merged

More hydra gtk#1047
vanhauser-thc merged 10 commits intovanhauser-thc:masterfrom
elboulangero:more-hydra-gtk

Conversation

@elboulangero
Copy link

No description provided.

As gtk_hbox and gtk_vbox are deprecated
The new autogen.sh was copied from
https://wiki.gnome.org/Projects/GnomeCommon/Migration

Then some files were updated to today's standard, so that at this point,
running ./autogen.sh doesn't spit out any warning.
Alternative would be to drop all those files entirely
This is something that distributions (at least Debian) has to patch,
because we want to be notified if something fails to build, we don't
want that a part of the package fails to build silently.

Looking at pw-inspector, it's a small C programm with no dependency, so
why would it fail to build anyway?

xhydra build is already conditioned by XHYDRA_SUPPORT: users who don't
want it can just build in a environment without GTK, if ever for some
reason it fails to build.
Following the logic of the last commit: no need to let it fail silently
or to wrap commands, hide output, etc etc... Just run the standard
commands, that's it.

xhydra:
-cd hydra-gtk && sh ./make_xhydra.sh
cd hydra-gtk && sh ./make_xhydra.sh
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if xhydra cannot be built then this should not result in a build failure. not everyone has gtk installed.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you don't have GTK devel files installed, the build of xhydra is just skipped, per:

all: pw-inspector hydra $(XHYDRA_SUPPORT)

XHYDRA_SUPPORT can be disabled manually:

thc-hydra/configure

Lines 108 to 113 in e92ccfd

if [ "X" = "X$XHYDRA_SUPPORT" ]; then
XHYDRA_SUPPORT_TMP=`echo "$1"|sed 's/.*--disable-xhydra//'`
if [ -z "$XHYDRA_SUPPORT_TMP" ]; then
XHYDRA_SUPPORT="disable"
fi
fi

Otherwise it's automatically set:

thc-hydra/configure

Lines 1332 to 1345 in e92ccfd

if [ "X" = "X$XHYDRA_SUPPORT" ]; then
echo "Checking for GUI req's (pkg-config/gtk+-3.0) ..."
XHYDRA_SUPPORT=`$PKG_CONFIG --help > /dev/null 2>&1 || echo disabled`
if [ "X" = "X$XHYDRA_SUPPORT" ]; then
XHYDRA_SUPPORT=`$PKG_CONFIG --modversion gtk+-3.0 2> /dev/null`
else
XHYDRA_SUPPORT=""
fi
if [ "X" = "X$XHYDRA_SUPPORT" ]; then
echo " ... NOT found, optional anyway"
else
echo " ... found"
fi
fi

Tell me if I'm missing something

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm well, let's try it if too many people complain then it can still be made optional again

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, don't hesitate to ping me if something comes out!

@vanhauser-thc
Copy link
Owner

looks good, left one comment. thanks!

@elboulangero
Copy link
Author

Also, I wanted to comment on this commit from this MR: 7b2c625

Personally, I'd be in favor of dropping all these generated files (that nobody is going to review), which means that users who want to build it HAVE TO run the ./autogen,sh script (which basically runs autoreconf). I don't think that it's going to be a problem for anyone.

I have no idea what's the "state of art" in this regard, I switched to meson long ago for GTK apps, as did much of the GNOME ecosystem. Looking for an example of a "modern" GTK app that still use autoreconf, I could find the 2.x branch of GIMP, and they don't commit those auto-generated files either: https://github.com/GNOME/gimp/tree/gimp-2.10.

So I'd prefer to drop all these files if that's Ok with you.

@vanhauser-thc
Copy link
Owner

Also, I wanted to comment on this commit from this MR: 7b2c625

Personally, I'd be in favor of dropping all these generated files (that nobody is going to review), which means that users who want to build it HAVE TO run the ./autogen,sh script (which basically runs autoreconf). I don't think that it's going to be a problem for anyone.

I have no idea what's the "state of art" in this regard, I switched to meson long ago for GTK apps, as did much of the GNOME ecosystem. Looking for an example of a "modern" GTK app that still use autoreconf, I could find the 2.x branch of GIMP, and they don't commit those auto-generated files either: https://github.com/GNOME/gimp/tree/gimp-2.10.

So I'd prefer to drop all these files if that's Ok with you.

sure then drop them

@elboulangero
Copy link
Author

Dropped the generated files and pushed last minor changes

@vanhauser-thc
Copy link
Owner

thanks!

@vanhauser-thc vanhauser-thc merged commit fbd8a1f into vanhauser-thc:master Nov 22, 2025
1 check failed
@vanhauser-thc
Copy link
Owner

I noticed that the autconfigure stuff now modifies the hydra-gtk/INSTALL file

@elboulangero
Copy link
Author

hydra-gtk/INSTALL yes it's a auto-generated file, I thought that it would be nice to keep it committed to the repo, in case someone wants to read it.

But then depending on what version of autoreconf you run, it will probably be slightly different...

So maybe best to remove it from the repo like all the other files? Agree with that?

@vanhauser-thc
Copy link
Owner

We could rename it to README.txt?

@elboulangero
Copy link
Author

README-autoconf? I pushed it here: #1048

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants