I think we need to differentiate here the difference in a non-commercial use restriction and the use of GPL code.  As fas as I know there is no restriction with GPL code to using it for commercial purposes, only that source code still needs to be made available.  The specific code in question, however, is explicitly licensed for non-commercial use only regardless of whether the code for the given product is made available or not.  These are 2 different conditions and I don't think it's appropriate to lump them together.

Chuck Atkins
R&D Engineer
Kitware, Inc.
(518) 371-3971 x603

-- "Mathematicians are tools for turning coffee grounds into formulas.", Paul Erdos

On Wed, Jan 13, 2010 at 8:31 AM, <peter@vanroose.be> wrote:
Joe Mundy wrote:
> Ok, so let's go with

The goal of this new setting is to avoid that people who want to build a commercial application using vxl, won't by accident use
GPL (or similar) source code. So by default, this setting must be ON.
The C++ source will thus need a
around GPL code.

So I see a disadvantage with this solution: people who build the code *without* any setting (e.g. because they don't use CMake, or
and old version of the generated makefiles, or whatever) will accidentally *include* the GPL code!

Therefore, if indeed BUILD_COMMERCIAL should be the default --which is to be overridden only *on purpose*-- shouldn't we
preferably use something like
as a CMake setting, which is then of course *not* set by default? In that case, the conditioning around GPL code would instead

--      Peter.

This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
Vxl-maintainers mailing list