<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
<BR>> CC: sebastian.huber@embedded-brains.de; rtems-users@rtems.org<BR>> From: daronchabot@gmail.com<BR>> Subject: plugin mods<BR>> Date: Sun, 23 Nov 2008 21:21:44 -0600<BR>> To: robert.fu@live.com<BR>> <BR>> I've committed several modifications & additions to the plugin. Check <BR>> out the CVS version tag v0_1.<BR>> <BR>> Sebastian, Robert: lemme know if this version works for you as <BR>> expected on Linux and Windows (respectively), 'cause it works on my <BR>> Mac :-)<BR>
<BR>
This is great news! Thanks a lot for making it work on Mac! I also had a sense<BR>
of relief, since now it's been proved that it also worked on another platform <BR>
after modifications. I guess like other things, once it's done, it looks much easier <BR>
than it initially appears to be.<BR>
<BR>
I checked out source as you instructed, and it still works on Windows. The HelloWorld program<BR>
generated from your new template was build successfully, and remote debugging<BR>
also worked for the program generated from the 1st template.<BR>
<BR>> <BR>> Mods include:<BR>> 1) removing arch/os limitations for host machine<BR>
<BR>
I took a look at your changes to plugin.xml, as what you mentioned before, <BR>
it seems that hard-coded arch/os (win32) in plugin.xml is one of the main reasons<BR>
why it did not work on Mac initially. <BR>
<BR>> 2) remove unnecessary flags/options<BR>> 3) add more stringent testing for the value of <BR>> RTEMS_BSP_DEFINED_SYMBOLS. Robert, i don't think any of the values <BR>> you state for this var in the wiki are required.<BR>
<BR>
Your reason of removing shared libgcc makes sense to me. For removing -D_REENTRANT<BR>
and your comments about RTEMS_BSP_DEFINED_SYMBOLS, which contains<BR>
macro like -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 ...<BR>
I don't know if it's right. <BR>
<BR>
These macros including -D_REENTRANT come with the generated Makefiles<BR>
like the Makefile for HelloWorld example. I guess removing it might not cause<BR>
compilation or link to fail, but you might actually get different code to <BR>
be included or linked.<BR>
<BR>
> <BR>> Addition of a simpler, "Hello World" template. In fact, it is just <BR>> the code from testsuites/samples/hello. Note, the page immediately <BR>> following the New C Project & Executable->Rtems Hello World Template: <BR>> this is just a quick & dirty example of how we could override <BR>> settings from a Preference Page.<BR>
<BR>
I saw them. Looks nice.<BR>
<BR>> <BR>> I'll commit a Preference addition to the plugin (probably tomorrow). <BR>> This will provide a semi-static place to store critical variables like:<BR>> 1) RTEMS_INSTALL_LOCATION (eg: /opt/rtems)<BR>> 2) RTEMS_ARCH: (eg: i386)<BR>> 3) RTEMS_BSP: (eg: pc386)<BR>> <BR>> Like I said before, that way we only pollute Eclipse's environment <BR>> variables and we'll have a (consistent) way to access them through <BR>> the build system and plugin machinery.<BR>
<BR>
Agree, it's better. <BR>
<BR>> <BR>> I going to go sulk now, 'cause Calgary won the Grey Cup... :-( I <BR>> think some sorrow drowning is in order.<BR>> <BR>> <BR>> -- dc<BR>> <BR>> BTW -- Sebastian, what's up with the cvs project <BR>> "org.rtems.cdt.toolchain2" ??<BR><BR><br /><hr />Color coding for safety: Windows Live Hotmail alerts you to suspicious email. <a href='http://windowslive.com/Explore/Hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_safety_112008 ' target='_new'>Sign up today.</a></body>
</html>