BurntSushi/rust-pcre2

Statically link against the existing PCRE2 library as reported by pkg-config

Open

#19 opened on Feb 22, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (40 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (63 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

By referring to the comments of pcre2-sys/build.rs, it appears to me that statically linking against an existing PCRE library is not supported yet. https://github.com/BurntSushi/rust-pcre2/blob/710307d8e13d3f5a674661206f55528032e607b3/pcre2-sys/build.rs#L3-L9

I would like to ask for supporting linking ripgrep to a PCRE static library.

Here is my use case: I built HAProxy, ripgrep, and other stuff inside a docker image. As the HAProxy was built with the latest PCRE2 library statically bounded, I naturally expect that the ripgrep could be bounded with the same library to cut off the compilation time and benefit from bumping of dependencies.

Contributor guide

Research direction
Examine the pcre2 sys/build.rs build script and add support for statically linking against an existing PCRE2 library using pkg config. The goal is to allow users to specify a path to a pre built PCRE2 static library, reducing compilation time and enabling consistent library versions across projects.
Tech stack
rustc
Domain
cli
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustCbuild systems
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30