You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- 1+1 for addressing the issues of derived vs aggregating. So far I've been able to avoid the LGPL for commercial products so I haven't needed to understand exactly what I would need to do.psr– psr2011-12-15 19:48:04 +00:00Commented Dec 15, 2011 at 19:48
- @psr - the LGPL is designed for commercial software. All you have to do is to bundle the LGPL part as a dll/so and make available the source to the LGPL lib (and any mods to it) online. You can even abide by the LGPL with a static linked app with a bit more effortMartin Beckett– Martin Beckett2011-12-16 16:56:10 +00:00Commented Dec 16, 2011 at 16:56
- @MartinBeckett - My understanding that a static linking is a problem, at it means people cant easily compile their own version of the library (to fix a bug for instance) and substitute for the on used by your app. It is the substitutability thats important.Mark Booth– Mark Booth2011-12-17 00:40:00 +00:00Commented Dec 17, 2011 at 0:40
- @Mark you can have a static app if you also allow the users to relink it with a new version of the LGPL lib, typically this means supplying your object files - although you could provide some sort of patch utility that would let them relink the LGPL lib. Unless you are on some sort of embedded platform without dynamic linking it's easier to just use so/dllMartin Beckett– Martin Beckett2011-12-17 18:18:45 +00:00Commented Dec 17, 2011 at 18:18
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you