[CMake] Best practices when using CMake 2.6 and Eclipse CDT 6.0

[Eric Noulard]

2009/10/11 Romain CHANU <romainchanu at gmail.com>:
> Thank you for your quick reply.
>
> Eclipse should be the one to fix this issue... Do you know if there is any
> request for it in Eclipse development?

Eclipse fixing the issue means:
"someone concerned with this particular problem provide
 patch or manpower to do it".

I don't think "eclipse developer" will fix this for CMake user unless
some of them are concerned by the issue.

When I face the issue back in 2007 I did ask some question
on CDT devel mailing list:
http://dev.eclipse.org/mhonarc/lists/platform-cvs-dev/msg00462.html

in the end the only solution I saw was the one suggested by Alex
previously in this thread, try to step in Eclipse CDT  and/or Eclipse Platform
dev and try to provide some patches for fixing this.

At that time just "requesting" the feature doesn't seems to offer a great
chance of success. Just as usual with open source software:
only asking without contributing has very small chance to succeed.

My **personal** conclusion was that I did not have time to do that.
Mainly because I do not have any eclipse internal development experience.

Those "ideas/thought" must be far outdated and I suggest you step in
cdt-devel or eclipse-platform mailings list and ask about an update regarding
that topic. Then come back to us in order to have a up-to-date status about
the 'out-of-source' support in *current* eclipse CDT/Platform.

> So if I sum up what we have said for this topic, the best solution would be
> to use Method 2 to make sure we do not lose the SVN tags, but doing this
> way, we do not use the CDT4 Generator...

This is currently my favorite way to use CMake+Eclipse+ any VCS.

> Am I correct Bill or do you have any other solutions?

I let Bill answer that one.

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org