vanhauser-thc/thc-hydra

Feature Request - use pkgconfig to detect build dependencies

Open

#450 opened on Sep 15, 2019

View on GitHub
 (5 comments) (1 reaction) (0 assignees)C (8,689 stars) (1,913 forks)batch import
enhancementgood first issuehelp wanted

Description

Currently configure assumes that all build dependencies are located in a fixed set of locations. Ideally use pkgconfig (which is needed for gtk anyway) to detect the dependencies so arbitrary dependency locations are supported.

Contributor guide

Tech stack
cshell
Domain
build systemtooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
understanding of autotoolsfamiliarity with pkgconfigbasic C build knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
The issue requests replacing hardcoded dependency paths in the configure script with pkgconfig detection. Look at the existing configure.ac and configure files in the repository. The solution involves using PKG CHECK MODULES macro for each dependency (e.g., gtk, openssl). Check the comments for any additional context or previously attempted fixes. Ensure that the changes are backward compatible and fall back to manual detection if pkgconfig is unavailable.
Feature Request - use pkgconfig to detect build dependencies · vanhauser-thc/thc-hydra#450 | Good First Issue