[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Hey gang, FYI,
As I mentioned on the last call, I've been asked to play a more active role in TCF and help build a community for it and work with you to bring it to maturity. That's taking most of my time these days as I get up to speed and figure out what we need to do with it.
In my spare time, I'm working on bringing the CDT to the Android community to help build native libraries for that platform. The focus is on one of my dream projects, building a game engine out of open source parts, in this case for Android, but I have eyes on iPhone and MeeGo too. Part of doing that is getting the Android gnu toolchain working well with CDT. And that's brought me back into the CDT build nightmare. Once again, I am having a hell of a time getting scanner discovery working for these seemingly simple Makefile projects. Just look at a stack trace sometime and you'll see, today, the CDT build system is the opposite of simple.
So I am urging myself to get back into working on a new build system. We need to put the architecture back to the way it was, with managed build being an add-on, not having everything driven by managed build. Obviously, I'm not going to have much time to spend on it, so by definition, I'll have to keep it simple. And I'll have to do it as a separate stack, not as an evolution of what we have.
Over the next few days, I'll jot down some more ideas here
http://wiki.eclipse.org/CDT/NextGenBuild. And I'll recreate cdt.build.* plug-ins, this time in a separate folder to avoid confusion. And as always help is appreciated and hopefully, I'll have new found vested interest in bringing it to completion, especially since I want to get back working on the Android project.
Cheers,
Doug