It seems people have a hard time understanding the implications of licenses, so I have written a something to help with that.

  • paequ2@lemmy.today
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    LGPL

    The license seems to be targeted towards languages like C/C++. On the other hand, languages like Go do a lot of static linking, so it may be impossible to comply with this license in Go.

    MPL may be a good alternative here.

      • paequ2@lemmy.today
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        2 months ago

        If you statically link against an LGPLed library, you must also provide your application in an object (not necessarily source) format, so that a user has the opportunity to modify the library and relink the application.

        Yeah, I think this is the hard part with Go. I’ve never seen anyone do anything with objects in Go. Everything is compiled into 1 binary, often statically linked. I’m not sure it’s possible to build a Go binary by using object files.