[graalvm-users] Creating maven artifacts for native libs

[Ramsey Gurley]

I think I have gotten ahead of myself. I decided to try to build libogg 
using graalvm first, since ogg is very small. My first problem is to 
build with clang and get .bc files out of the build process. If I

CC=/usr/bin/clang ./configure && make

then it will build with clang and I get the expected .so files, but if I

CC=/usr/bin/clang CFLAGS=-emit-llvm ./configure && make

then it fails very quickly in the configure script.

# CC=/usr/bin/clang CFLAGS=-emit-llvm ./configure && make
checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking how to print strings... printf
checking for gcc... /usr/bin/clang
checking whether the C compiler works... no
configure: error: in `/libogg-1.3.4':
configure: error: C compiler cannot create executables
See `config.log' for more details

I'm more familiar with java than C, so I'm wondering if I did something 
incorrectly. Has anyone has had better luck with building native libs 
with graalvm?

Thanks,

Ramsey

On 11/25/19 4:47 PM, Ramsey Gurley wrote:
> Hi all,
>
> I'd like to compile a native lib with graal to be distributed as a 
> maven artifact. I have a few questions.
>
> Are native libraries platform specific if compiled with graalvm's llvm 
> tools? Let's say I want to compile x265. Do I need one artifact per 
> arch? Per os?
>
> Once created, can the graal compiler used by OpenJDK make use of them? 
> Or is a graalvm with llvm tools installed a requirement?
>
> Basically, I want to fill a gap in Java, which is video codecs and a 
> swing component to use them. I'm hoping graalvm is a good way to do this.
>
> Thank you,
>
> Ramsey
>