mattn / mattn/mruby-onig-regexp

No way to explicitly use the included libonig instead of what is installed on the host system

Open
#110 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
31
Forks
40
PR merge metrics
No merged PRs in 30d

Description

My build machine has libonig installed for reasons unrelated to mruby. When I build my project, it links against that version instead of the one that comes with the gem. Since the installed libonig is a shared library and the project is intended to produce a distributable binary, this is a problem.

I would like a way to force the gem to always use its own version of the library even if there's a version present on the system.

I've coded the change and will submit a pull request.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Inspect the gem's build and library-discovery configuration, starting with how it currently chooses between the bundled libonig and a host-installed library. Done means the build can explicitly select the included library and produce a distributable binary without linking the host shared library.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
build-system
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.