<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Hi Chris,<BR>
<BR>
> I have not followed in detail where they are getting the info from but <BR>> Makefiles would concern me.<BR>
<BR>
Yes, this part need be re-examed. I also had some concerns initially, <BR>
and worried that the Makefile referenced might not be generic enough.<BR>
Also currently no additional processing is done after the link step.<BR>
<BR>
I checked the BSP config files after you mentioned it, and it<BR>
looks like we can extract some information there. I also have a couple <BR>
of questions:<BR>
<BR>
1. The configure command I used was:<BR>
<BR>
/opt/src/rtems/rtems-4.9.0/configure --target=i386-rtems4.9 --enable-rtemsbsp=pc686 --enable-cxx --enable-rdbg --prefix=/opt/rtems_install<BR><BR>
And I got the following in \opt\rtems_install\i386-rtems4.9\pc686\make\bsp.cfg<BR>
<BR>
##<BR>## Does this BSP support RTEMS's remote debugger ?<BR>##<BR>HAS_RDBG = no<BR><BR>
And the following in target.cfg;<BR>
<BR>
RTEMS_HAS_RDBG = no<BR>
<BR>
Which is wrong? My configure option or the cfg files?<BR>
<BR>
2. It looks like the Makefiles in the those sample programs (e.g., HelloWorld)<BR>
contains extra defined symbols determined by the configure script for <BR>
sample program. The following is an example:<BR>
<BR>
DEFS = ...... -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_CSTDIO=1 -DHAVE_CSTDLIB=1 -DHAVE_IOSTREAM=1<BR><BR>
I thought these symbols indicate the capability of the target gcc system. <BR>
None of such symbols is included in the installed BSP files. When we compile<BR>
user programs, should we include these symbols like what's in those sample<BR>
programs?<BR>
<BR>
3. For "CFLAGS= -g -O2 -D_REENTRANT -shared-libgcc" <BR>
It's said that RTEMS is linked statically, so "-shared-libgcc" should not be used.<BR>
Should "-shared-libgcc" be used? Is "-D_REENTRANT" needed?<BR>
<BR>
Thanks a lot for your help!<BR>
<BR>
Robert Fu<BR>
<BR><BR>> Date: Tue, 25 Nov 2008 11:17:01 +1100<BR>> From: chrisj@rtems.org<BR>> To: joel.sherrill@oarcorp.com<BR>> Subject: Re: plugin first steps<BR>> CC: sebastian.huber@embedded-brains.de; robert.fu@live.com; rtems-users@rtems.org<BR>> <BR>> Joel Sherrill wrote:<BR>> > It seems like you are working to extract information<BR>> > from the RTEMS Application Makefiles and generate<BR>> > some configuration information for Eclipse. Chris<BR>> > has been working to eliminate them in favor of autoconf<BR>> > for the external examples.<BR>> > <BR>> <BR>> I have not followed in detail where they are getting the info from but <BR>> Makefiles would concern me.<BR>> <BR>> The approach taken in the autoconf examples is to use the BSP configuration files.<BR>> <BR>> Does Eclipse have support for autotools ?<BR>> <BR>> > Couldn't the same information be directly generated<BR>> > by RTEMS?<BR>> <BR>> It is held in RTEMS already in the BSP config files. This file is installed <BR>> when the BSP is installed.<BR>> <BR>> Regards<BR>> Chris<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>