<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>
I have no objection to removing the unused libraries. Thanks for catching it.<BR>
<BR>
For the "first steps" type of references, there is also another place contains <BR>
more detailed information: "Managed Build System Extensibility Document"<BR>
(mentioned in referrence section in my previous email) contains a section called <BR>
"Tutorial: An Example Tool Integration". It worked well for me. The initial<BR>
version of the plug-in was built upon what I got after following the tutorial<BR>
step by step. <BR>
<BR>
Somebody said "Managed Build System Extensibility Document" is the bible<BR>
for CDT plug-in development, and I believed it. In fact this 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>
Although I don't know how actually Sebastian plan to do it, I think if we can <BR>
automatically extract settings/configurations from Makefiles generated<BR>
by configure process, it's an improvement over the current one since it'd <BR>
require less user input. <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, Sebastian <BR>
has openSuSE 10.3 env and you have Mac env. <BR>
<BR>
I assume that we cannot get all we want in one shot, so one of many possible <BR>ways to move forward is:<BR>
<BR>
1. Make the 1st version work in Linux and Mac; Once it works in one OS, re-test<BR>
it in the other OS until we get one version that works in each 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 one OS, <BR>
re-test the new plug-in in the other OS. We go through this iterative process <BR>
until we think we have all necessary features.<BR>
<BR>
Thanks,<BR>
Robert Fu<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-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>> <A href="http://rtems.rtems.org/mailman/listinfo/rtems-us">http://rtems.rtems.org/mailman/listinfo/rtems-us</A><BR><br /><hr />Get more done, have more fun, and stay more connected with Windows Mobile®. <a href='http://clk.atdmt.com/MRT/go/119642556/direct/01/' target='_new'>See how.</a></body>
</html>