Fork me on GitHub
#lumo
<
2019-04-18
>
richiardiandrea18:04:46

I was checking how to compile lumo statically and I bumped into this commit that @grav made against a lumo fork https://github.com/grav/lumo/commit/78d04752231f362b34c368be008b5240a25b7797

richiardiandrea18:04:20

Has there been some talk already around adding it to lumo proper?

richiardiandrea18:04:15

The problem I am trying to solve is that the latest lumo need a higher version on some dynamic libraries that the AWS lambda runtime does not support

anmonteiro18:04:19

@richiardiandrea yes, lumo has been statically compiled before

anmonteiro18:04:22

but it’s just not feasible

anmonteiro18:04:32

otherwise native modules don’t work

richiardiandrea18:04:45

Oh ok that's why

anmonteiro18:04:18

they only work if you compile them against the musl version that was statically linked in

richiardiandrea19:04:47

By native modules you mean util, fs, or npm modules that are compiled to native?

anmonteiro19:04:11

.node modules

anmonteiro19:04:28

native “extensions” or whatever they’re called

anmonteiro19:04:01

perhaps we could add a statically compiled Lumo to the build matrix

richiardiandrea19:04:33

Yeah that would be awesome because the AWS runtime use case is so attractive

anmonteiro19:04:45

I’m not gonna do it but feel free to send a PR

richiardiandrea19:04:55

And at the moment I am using Grav's binary

anmonteiro19:04:18

it should really just be a matter of adding that flag conditionally on an env variable or something

richiardiandrea19:04:30

Yep I think that should an easy one