this post was submitted on 12 Jan 2024
1073 points (97.7% liked)
Technology
59377 readers
4340 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Not just license. You also need to link to it as a shared library and allow users to replace it with their own build of the library. Meaning you can't use stuff like DRM and anticheats.
Yup fair point I didn't know that. Unity presumably does this with dlls that a technical user can easily swap out. In principle an asset store script could do this, but it would be very difficult to verify and enforce so I can see why they'd just ban the license outright as a CYA thing.
Maybe the answer is to distribute a vlc dll separately and only ship a linking/driving script via the asset store.
Technically it can be statically linked, but then you would need to provide artifacts (for example, object files for the non-LGPL modules) enabling the end user to "recombine or relink" the program with a modified version of the LGPL code.
Dynamic linking is usually simpler, though. And the DRM issues apply either way.