<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Hi Daron,<BR>
<BR>> However, upon closer analysis, it became clear that in order to <BR>> maintain a useful degree of independence from the RTEMS build-system <BR>> and maximum flexibility, the Managed Build approach is *the* way to go.<BR><BR>
Agreed. I also thought about whether we need support "Standard Makefile" <BR>
type of project.<BR>
<BR>
Beside the CVS repo you mentioned earlier, the official CDT release also come<BR>
with CDT source code, and being able to browsing and debugging/tracing into <BR>
CDT source code helped me in the development.<BR>
<BR>
If you and Sebastian send me the error messages, commands invoked and <BR>
the Makefile generated for the HelloWorld example on your system (via private <BR>
email, not the whole list), perhaps I can better understand what problems <BR>
you're currently facing on your system.<BR>
<BR>
Thanks,<BR>
Robert Fu<BR>
<BR>> From: daronchabot@gmail.com<BR>> Subject: Re: plugin first steps<BR>> Date: Sat, 22 Nov 2008 13:16:49 -0600<BR>> To: robert.fu@live.com<BR>> CC: sebastian.huber@embedded-brains.de; rtems-users@rtems.org<BR>> <BR>> <BR>> On 22-Nov-08, at 3:38 AM, Robert Fu wrote:<BR>> <BR>> > For the "first steps" type of references, there is also another <BR>> > place contains<BR>> > more detailed information: "Managed Build System Extensibility <BR>> > Document"<BR>> > (mentioned in referrence section in my previous email) contains a <BR>> > section called<BR>> > "Tutorial: An Example Tool Integration". It worked well for me. The <BR>> > initial<BR>> > version of the plug-in was built upon what I got after following <BR>> > the tutorial<BR>> > step by step.<BR>> ><BR>> > Somebody said "Managed Build System Extensibility Document" is the <BR>> > bible<BR>> > for CDT plug-in development, and I believed it. In fact this <BR>> > document plus<BR>> > "What's New in CDT Build System 4.0" are the only 2 documents that<BR>> > guided me for the developement of initial RTEMS plug-in.<BR>> <BR>> Yah, I've been through the "MBS Extensibility" doc, and it *is* the <BR>> "bible" for CDT plugin development. But, there are other good sources <BR>> too, the CDT sources being an example. Another is the CDT extension <BR>> point reference docs:<BR>> <BR>> http://help.eclipse.org/help33/index.jsp?topic=/ <BR>> org.eclipse.cdt.doc.isv/reference/extension-points/index.html<BR>> <BR>> Although these refer to eclipse 3.3, they are still very much <BR>> relevant to the CDT as found in eclipse 3.4.<BR>> <BR>> > Although I don't know how actually Sebastian plan to do it, I think <BR>> > if we can<BR>> > automatically extract settings/configurations from Makefiles generated<BR>> > by configure process, it's an improvement over the current one <BR>> > since it'd<BR>> > require less user input.<BR>> <BR>> That approach implies some type of parser is required. I'm sure <BR>> Sebastian will communicate his ideas here as soon as he's able.<BR>> <BR>> Only a couple of years ago, the CDT had two types of projects: <BR>> Managed Build and Standard Makefile. Both are still present, only in <BR>> a more refined form. Managed build projects construct Makefiles <BR>> automatically, while Standard Makefile projects simply rely on the <BR>> user to provide a (Makefile-based) build system.<BR>> <BR>> The RTEMS-Eclipse plugin I was designing would utilize the RTEMS <BR>> makefile templates, Makefile.leaf, Makefile.lib, and Makefile.dir <BR>> (found in ${RTEMS_INSTALL_LOCATION}/make/Templates), *in conjuction* <BR>> with user-provided values like executable name, etc.<BR>> <BR>> However, upon closer analysis, it became clear that in order to <BR>> maintain a useful degree of independence from the RTEMS build-system <BR>> and maximum flexibility, the Managed Build approach is *the* way to go.<BR>> <BR>> > One other improvement I can see is to make it work on Linux and Mac.<BR>> > It seems we 3 have right mix of environments: I have Windows one, <BR>> > Sebastian<BR>> > has openSuSE 10.3 env and you have Mac env.<BR>> <BR>> Having the plugin work across the 3, main OSes is not just an <BR>> improvement, it's a *necessity * :-)<BR>> <BR>> Of course, we should strive for OS-independence as much as possible...<BR>> <BR>> I would also lump RTEMS target arch and BSP selection as necessities.<BR>> <BR>> > I assume that we cannot get all we want in one shot, so one of many <BR>> > possible<BR>> > ways to move forward is:<BR>> ><BR>> > 1. Make the 1st version work in Linux and Mac; Once it works in one <BR>> > OS, re-test<BR>> > it in the other OS until we get one version that works in each <BR>> > of the 3 OS. We<BR>> > then use it as a comman base for further refinement.<BR>> ><BR>> > 2. Add new improvements one by one. After one new feature works in <BR>> > one OS,<BR>> > re-test the new plug-in in the other OS. We go through this <BR>> > iterative process<BR>> > until we think we have all necessary features.<BR>> <BR>> Yes. An iterative development scheme is the only way to go.<BR>> <BR>> We need to get a solid base to build upon. First focusing on the <BR>> basic toolchain elements: assembler, c/c++ compiler & linker, <BR>> archiver. Debugger and Launch configs are almost as important. But we <BR>> have to be able to build something to run and debug first :-)<BR>> <BR>> I'm still studying your plugin trying to get up to speed... thanks <BR>> again.<BR>> <BR>> ><BR>> ><BR>> > > From: daronchabot@gmail.com<BR>> > > Subject: plugin first steps<BR>> > > Date: Fri, 21 Nov 2008 21:05:17 -0600<BR>> > > To: robert.fu@live.com<BR>> > > CC: sebastian.huber@embedded-brains.de; rtems-users@rtems.org<BR>> > ><BR>> > > Robert,<BR>> > ><BR>> > > Thanks for your contribution. It looks like a good place to start.<BR>> > ><BR>> > > I sent the link below to Sebastian in an earlier email.<BR>> > ><BR>> > > If you have not already done so, I recommend checking out the cdt- <BR>> > all<BR>> > > CVS module from the Eclipse repo. You can find directions here:<BR>> > ><BR>> > > http://wiki.eclipse.org/Getting_started_with_CDT_development<BR>> > ><BR>> > > The best place to learn how things work is the reference<BR>> > > implementations contained in the "cdt-all" CVS module.<BR>> > ><BR>> > > If you and Sebastian have no objections, I'd like to remove the<BR>> > > unused library dependencies from the plugin's ".settings" file,<BR>> > > partly to see if I can commit to the RTEMS cvs repo and partly to<BR>> > > clean things up a bit.<BR>> > ><BR>> > > Those dependencies are:<BR>> > > 1) org.eclipse.cdt.core.lrparser_5.0.1.200809120802.jar<BR>> > > 2) org.eclipse.cdt.core.parser.upc_5.0.0.200809120802.jar<BR>> > ><BR>> > ><BR>> > > -- dc<BR>> > > _______________________________________________<BR>> > > rtems-users mailing list<BR>> > > rtems-users@rtems.com<BR>> > > http://rtems.rtems.org/mailman/listinfo/rtems-us<BR>> ><BR>> > Get more done, have more fun, and stay more connected with Windows <BR>> > Mobile®. See how.<BR>> <BR>> _______________________________________________<BR>> rtems-users mailing list<BR>> rtems-users@rtems.com<BR>> http://rtems.rtems.org/mailman/listinfo/rtems-users<BR><BR><br /><hr />Proud to be a PC? Show the world. Download the “I’m a PC” Messenger themepack now. <a href='http://clk.atdmt.com/MRT/go/119642558/direct/01/' target='_new'>Download now.</a></body>
</html>