User forums > Using Code::Blocks

New beginner's question about projects and small programs! Please help!

<< < (2/3) > >>

BCCISProf:

--- Quote ---That is not correct. A project can have 1..n targets. Each target can have one main() (if you like to call it that way). Notice that a target does not require to be an application at all. It can also be a library or just a script or even just a collection of files without any compilation. Within a workspace you can have 1..n projects. So it's: 1 workspace with 1..n projects with 1..n targets each.

--- End quote ---

You are quite correct. However, I was trying to describe it to someone who appears to be a student in an introductory programming class. In such a situation this simplification is probably warranted.

BCCISProf:

--- Quote from: dje on February 04, 2008, 11:20:29 pm ---Nice, but it seems that the source code is not available...
Looks like piracy isn't it ?

--- End quote ---

What are you referring to? I hope not to the manual.... :) After all, I am one of the authors.....

dje:
Hi !

As I read the manual, I was curious to see what was at the adress:
http://www.sci.brooklyn.cuny.edu/~goetz/codeblocks/

And it seems setups of MinGW and Code::Blocks are available without providing the sources whereas both are under GPL.

Dje

thomas:
Regarding the actual manual, it's hard to give a clear answer.
If it is (at least partially) derived from the docinfo like Mario's manual, then very strictly speaking, it falls under the GPL as derived work, and the author must publish sources (screenshots are mostly considered not to be protected by copyright, or may be defended by fair use in some countries, unless they predominantly or exclusively consist of copyrighted original artwork).

However, I generally think that in the case of documentation, a too strict interpretation of licenses such as the GPL is a bit pedantic and unsuitable.
Documentation is meant to make everyone's life happier, it helps users to understand a program, and it is very clearly beneficial to a program's acceptance (unless it's a really bad documentation). Thus, punishing people for writing documentation in obviously good faith looks a bit silly to me.

Regarding the binaries, Dje is right. The GPL does demand that you publish the sources for both MinGW and Code::Blocks if you offer downloads (a link to the source code is not enough). But no worries, the FBI won't knock down your front door during the next 8 hours, please just add the sources when you find the time.
Unluckily, it is not possible (other than by dual-licensing) to make exceptions on the source code clause for several legal reasons (which, to make it more difficult, are different in different countries, too).

If publishing the source code is a problem (due to bandwidth, or for whatever reason), it is still easy to make everyone happy by writing something like:
Download the MinGW installer: MinGW-5.1.3.exe

BCCISProf:

--- Quote --- Regarding the actual manual, it's hard to give a clear answer.
--- End quote ---

Let me be very clear. The manual is written from scratch -- it is not a derivative work. We wrote it for our students and are glad to make it available to anyone who might find it useful. In academic circles we take the hint of plagiarism very seriously. I want to make it clear that this is an original work.


--- Quote ---Regarding the binaries, Dje is right. The GPL does demand that you publish the sources for both MinGW and Code::Blocks if you offer downloads (a link to the source code is not enough)........
--- End quote ---

With regards to CodeBlocks and MinGW we have packaged it, with the options our students need, in what we hope is a foolproof uncomplicated installation for introductory students in computer science.

In order to comply with GPL licensing, we are happy to adopt Thomas' suggestion. Thus we have modified our page http://www.sci.brooklyn.cuny.edu/~goetz/codeblocks/ to include the source code.

Navigation

[0] Message Index

[#] Next page

[*] Previous page