statically linking libheif

[woelper]

Hi, and thank you for this great library!

I am trying to statically link libheif to make distribution of my program easier and not have the user install libheif individually. Is there a recommended or even built-in way of doing so?

[Cykooz]

I'm afraid, I don't know how to do it. I've never done it before.

[neckaros]

Hi, and thank you for this great library!

I am trying to statically link libheif to make distribution of my program easier and not have the user install libheif individually. Is there a recommended or even built-in way of doing so?

I'm pretty new to rust but doesn't rust embed libraries in executable at build time?

[sophie-h]

I'm pretty new to rust but doesn't rust embed libraries in executable at build time?

C libraries are manually dynamically linked. This has nothing to do with how rust crates work.

[JokerAJP]

How to support compiling into wasm?

[Cykooz]

How to support compiling into wasm?

According to the Internet it is a very painful task.

[Cykooz]

Also you have to consider that libheif is licensed under LGPL v3.

So if you want to distribute a combined work, you'll have to use the following license:

• statically linked:
  • Either you must release both parts as LGPL.
  • Or provide everything that allow the user to relink the application with a different version of the LGPL source code. In this case the other requirements are the same as if it was dynamically linked.
• dynamically linked: LGPL code stays LGPL, you can keep the proprietary code proprietary.

Source - https://stackoverflow.com/a/10179181

[neckaros]

Hi, and thank you for this great library!

I am trying to statically link libheif to make distribution of my program easier and not have the user install libheif individually. Is there a recommended or even built-in way of doing so?

@woelper Did you succeed in statically linking libheif ?