# Create a cross haxelib consuming a C library?

**URL:** <https://community.haxe.org/t/create-a-cross-haxelib-consuming-a-c-library/3265>\
**Category:** Haxe\
**Created:** [September 24, 2021, 12:41pm UTC](https://community.haxe.org/t/create-a-cross-haxelib-consuming-a-c-library/3265 "2021-09-24T12:41:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lelelo1](https://avatars.discourse-cdn.com/v2/letter/l/9f8e36/32.png) [@Lelelo1](https://community.haxe.org/u/Lelelo1)\
**Post date:** [September 24, 2021, 12:41pm UTC](https://community.haxe.org/t/create-a-cross-haxelib-consuming-a-c-library/3265/1 "2021-09-24T12:41:34Z")

</div>

Is it possible to create a cross haxelib that consumes a C library?

---

<div class="post-metadata">

**Author:** ![RealyUniqueName](https://community.haxe.org/user_avatar/community.haxe.org/realyuniquename/32/10_2.png) [@RealyUniqueName](https://community.haxe.org/u/RealyUniqueName)\
**Post date:** [September 24, 2021, 1:08pm UTC](https://community.haxe.org/t/create-a-cross-haxelib-consuming-a-c-library/3265/2 "2021-09-24T13:08:48Z")

</div>

> **[GitHub - Aurel300/ammer: Unified FFI for Haxe native extensions](https://github.com/Aurel300/ammer)**
>
> Unified FFI for Haxe native extensions. Contribute to Aurel300/ammer development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![Lelelo1](https://avatars.discourse-cdn.com/v2/letter/l/9f8e36/32.png) [@Lelelo1](https://community.haxe.org/u/Lelelo1)\
**Post date:** [September 24, 2021, 1:20pm UTC](https://community.haxe.org/t/create-a-cross-haxelib-consuming-a-c-library/3265/3 "2021-09-24T13:20:12Z")

</div>

> [@Some questions about the ammer library (FFI, haxelib, externs)](https://community.haxe.org/t/some-questions-about-the-ammer-library-ffi-haxelib-externs/2271/2):
>
> First of all, thanks for the interest in ammer! I talked a bit about the motivation for this project [here](https://youtu.be/vfss5AYWCNM?t=1015). I admit the language surrounding externs, libraries, native libraries, and so on can be a bit confusing or ambiguous. For the purposes of ammer, a “native library” is a library distributed to end users as a .dll, .so, or .dylib file (on Windows, Linux, and Mac OS X, respectively). Such a library is typically written in C or C++, although it really doesn’t matter – in the end it just conta…