[CMake] *Updated* Eclipse CDT4 CMake Generator - Pre-Alpha version

[Miguel A. Figueroa-Villanueva]

Update patch and source.

On 7/31/07, Alexander Neundorf wrote:
> On Tuesday 31 July 2007 15:40, you wrote:
> > On 7/31/07, Alexander Neundorf wrote:
> > > From the header:
> > > enum ToolChainType { OTHER, LINUX, CYGWIN, MINGW, SOLARIS, MACOSX };
> > > I would prefer more specific names, e.g. prefixing them
> > > with "EclipseToolchain", so that you have EclipseToolchainCygwin etc.
> >
> > Even if it is a private enum?
>
> Yes, makes it easier to search for stuff in the sources.
>
> > Ok, I guess the following should do, right?
> >
> > enum EclipseToolchainType {
> >   EclipseToolchainOther,
> >   EclipseToolchainLinux,
> >   EclipseToolchainCygwin,
> >   EclipseToolchainMinGW,
> >   EclipseToolchainSolaris,
> >   EclipseToolchainMacOSX
> > };

Done.

> > > One thing which would be nice is if you would also put the include
> > > directories in the project files, I think this is required for
> > > autocompletion. You can get them via cmMakefile::GetIncludeDirectories().
> >
> > I thought about that and I'll do it, but the reason I hesitated was
> > because I don't know how to add them in a per cmake project basis. I
> > can include it in the toplevel (and only) .cproject, but that applies
> > to all projects beneath it, which isn't much of a problem since your
> > building with "make" anyhow.
> >
> > As far as I know however, eclipse cdt doesn't support nesting
> > .project/.cproject for hierarchichal project structures. Does any one
> > know more about this? I'm planning on asking these on the cdt list
> > eventually.
>
> So one include path for everything ?
> Then probably collect all used include paths in the whole tree and use them
> all.

Done.

--Miguel