Must you share licensing information for library dependencies? [closed] - licensing

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I'm not sure where on the Stack Exchange to ask this question.
If one of your project's dependencies is dependent on another library, do you share both licensing information?
For example, if my application uses Library A that is dependent on Library B, but my code doesn't depend on Library B, do I share licensing information for it (it as in Library B)? Do I attribute credit?

You are subject to the licenses of everything included in your program, whether included directly or indirectly (i.e. a dependency of a dependency). You'll have to check each license to see what obligations each imposes on you - some require disclosure to recipients, some don't.

Related

Carrot2 license for commercial project without website&documentation [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
According to carrot2 FAQ we should acknowledge project users about using Carrot2.
Can I use Carrot2 in a commercial project? Yes. The only requirement
is that you properly acknowledge the use of Carrot2 (on the project's
website and documentation) and let us know about your project. Please
also remember to read the license.
But we don't have and site or documentation because we are building closed project.
How can we integrate carrot2 in these circumstances?
I've revised the text on the license and FAQ pages to make the acknowledgment optional, but you still need to include Carrot2 license file in your binary distribution. A common practice is to put the license file next to the relevant JAR file.

how do you use public licenses? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
If i want to use a public license, is it as easy as copying the license and putting it in my source code/making a new file, or is there something special i need to do to use it?
Here's a guide on how to use GNU licenses in your project. From the guide:
The process involves adding two
elements to each source file of your
program: a copyright notice (such as
“Copyright 1999 Terry Jones”), and a
statement of copying permission,
saying that the program is distributed
under the terms of the GNU General
Public License (or the Lesser GPL).
Other public licenses should be similar, but be sure to check the website of the license you're using for specifics.
Just need to include the license and comply with it.

PostSharp 1.5 licencing [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
We are evaluating PostSharp for logging purposes to use in a our project (implemented in .Net). Currently it is running in production enviroment. Can mixing with PostSharp raise licencing issues? As far as I know it is partially free. Am I wrong? What future licencing problems (i.e. is PostSharp planning to be non-free for future releases) can we face, if there are any?
The PostSharp licensing FAQ explains this in great detail.
Can mixing with PostSharp raise licencing issues?
You're unlikely to have future problems if you don't link to the part that actually does the transformations (that's PostSharp.Core). PostSharp.Laos and PostSharp.Public are what most applications will typically link to.
As far as I know it is partially free. Am I wrong?
It's all free as in beer, unless you (1) link to Core and (2) need to distribute your app outside your company. In that case, you have to buy a license. Core is released under GPL.
See the licensing options, which neatly summarizes answers to both those questions at the top of the page.

BSD licensing - what do I put in the organisation tag, if I'm the sole programmer? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
Point three for example:
Neither the name of the ORGANIZATION nor the names of its contributors may
be used to endorse or promote products
derived from this software without
specific prior written
permission.
Thanks for any advice.
Have you considered using the MIT License as an alternative? It seems (to my eyes) to say about the same thing, but without the organization section.
When I used the BSD license I just reworded it so that it didn't mention organization.

Protecting licensing implementation in C++ [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
What ways are there to protect licensing enforcement mechanisms in C/C++?
I know of:
Using macros (but that make the code difficult to maintain)
Linking statically
Obfuscating symbol names
Other methods I am not sure about:
Using C++ templates
Using inline functions
It's usually a good idea to keep your code as clean as possible and rely on a third party tool to protect your code.
google for "c++ obfuscator" to find such tools.

Resources