lovell / lovell/sharp-libvips

Provide artifacts with libtool and pkg-config files

Open
#36 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Shell
Stars
212
Forks
132
Avg merge
5h 18m
Merged PRs (30d)
11

Description

Hi!

Thanks for maintaining sharp and these native libraries for libvips! They're a great help to get started. 😃

I'd like to use the native libraries provided by this project in https://github.com/criteo/JVips instead of building the libraries and maintaining their build scripts in JVips, too.

Since it's a Java project using JNI to interface with the native libraries, I need to compile a small wrapper which requires the pkg-config (*.pc) and libtool (*.la) files in order to be build.
Unfortunately, those files are removed at the end of the Linux build script:
https://github.com/lovell/sharp-libvips/blob/5007da5e52eaee573021ea71f69ec65a68c9f6bf/build/lin.sh#L284-L285

@lovell Do you think it would be possible and sensible to provider an additional artifact with just these files for people to use the pre-built libraries of sharp-libvips and link them to their own C wrappers?

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

Start by reading build/lin.sh around lines 284-285 and inspect how Linux artifacts are assembled and packaged. Determine how an additional artifact could retain the pkg-config (.pc) and libtool (.la) files for the pre-built libraries. Done means a published artifact contains those files and can support linking a JNI or C wrapper without rebuilding the libraries.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.