Static build

[ealione]

I've been using Operon just fine on the machine that I compiled it using nix build, but when I decided to copy the entire results folder that contains

results:
|-bin
|-include
|-lib
|_share

to a different machine, I couldn't run it because a whole set of different libraries were missing. How can I statically compile Operon so I can use it everywhere, without having to re-compile every time I want to move to a different system?

[ealione]

Running ldd will report many missing dependencies but also version mismatches like:

linux-vdso.so.1 (0x00007ffd7a0fe000)
libscn.so.4 => not found
libxxhash.so.0 => not found
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f81d349c000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f81d334d000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f81d3332000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f81d313e000)
/nix/store/wn7v2vhyyyi6clcyn0s9ixvl7d4d87ic-glibc-2.40-36/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00007f81d389c000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f81d311b000)

since I'm assuming Operon was originally built on a computer with newer versions of the standard libraries.

[foolnotion]

A fully static build is currently not supported. We will need to look into this.

[ealione]

I see, In that case I'll try to figure it out if I can. It would be nice to not have to build the cli apps multiple times.