[CMake] cmake support Dev C++

[Brandon Van Every]

On 7/30/07, Andy Dingfelder <DingfelderA at sirtrack.com> wrote:
>
> Personally, my motivation is that I want to use Eclipse on Linux to
> develop both java and c++ apps, and want them to run on mac, Linux and
> PC.  I have seen multiple discussions in a variety of places that talk
> about how to do this, some with better luck than others.  I see cmake as
> a natural fit for Eclipse as (IMHO) Eclipse is perhaps the most widely
> used *multi-platform* environment out there, running on basically any OS
> that java runs on, and everyone here knows the strengths of cmake, so I
> don't need to expand upon that.

CMake's level of Java support is a strategic risk.  Eclipse isn't just
a cross-platform crowd, it's a cross-platform heavily Java crowd.  So
if CMake's Java support is irritating to work with, that could put off
Eclipse tool developers, whatever CMake's C/C++ merits are.  On the
other hand, getting one's feet wet with Eclipse and Java would be a
good way to drive the improvement of CMake's Java support.  I would
just anticipate a lot of bumps, and invitations to substantial work.
I do think that light would ultimately be seen at the end of the
tunnel, however.

Code::Blocks doesn't have any Java encumbrance, it's a C/C++ developer
crowd.  Of course it doesn't have nearly the number of users as
Eclipse, nor the commercial acceptance and clout, so that's a
strategic risk.  I think someone would have to either be a
Code::Blocks diehard and really want to get it done, or else it would
have to be relatively easy to do.  Otherwise, nobody would bother.

Another risk with Code::Blocks is their release policy is immature.
They might have great stuff, but they can't seem to manage to put an
official binary distribution out there.  Instead one does this daily
snapshot download dance, grabbing 3 different files.  It suggests to
me that their architecture could be in flux, which could make CMake
support a moving target.  Chasing a handful of devs that don't really
value release maturity or commercial stability might be no fun at all.
 But I don't actually know their culture or the relative stability of
their code, so I won't pass judgment.  Be sure to research it before
diving in though.

The Eclipse community is very mature as far as their release policies.


Cheers,
Brandon Van Every