license code::blocks and wxsmith

[3rdshiftcoder]

Hi

I ran into a problem in Java because i selected bsd,lgpl,apache,sun,epl. When i wanted functionality, I would link to a class library (add a jar to my project). It is too late, and i had to kill the project.

So my question is am i linking to external libraries when I build the binary (.exe) that are going to get me in trouble like the Java project. I will probably use c++ standard and wxwidgets (LGPL). Beyond that i dont know what i am getting into. How can i avoid the trap of having to follow all the requirements of the GPL which i dont understand as I am not a lawyer? Is it common for people to build applications in code::blocks and wxsmith without having to follow the requirements of the GPL? Any help is greatly appreciated because I must NOT repeat the java problem (200+ hours wasted)!

thanks
3rdshiftcoder

[3rdshiftcoder]

Hi-

I found a post that reaffirmed that it is ok to use code::blocks and wxsmith in a project without having to distribute source code. Sorry, but i had to ask. I am really paranoid after my cool Java programmed flopped because of license issues.

http://forums.next.codeblocks.org/index.php/topic,939.0.html
http://forums.next.codeblocks.org/index.php/topic,8126.0.html

I'm off to go get my wxwidgets c++ book. I will pick c++ as python is in the middle of big changes, and c++ will remain very compatible even with the new standard coming.

very cool.

Thanks,
3rdshiftcoder

[MortenMacFly]

I found a post that reaffirmed that it is ok to use code::blocks and wxsmith in a project without having to distribute source code.

The projects you are developing using C::B can of course be closed source. However - if you are modifying C::B itself (or any of it's plugins) and distribute the modified version of C::B that you have to provide the source code, too. Of course this would also apply to an unmodiefied version.

[3rdshiftcoder]

ok-

very cool.
I can't wait to get started.

Thanks Morten.