This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Access version number string of eCos to check the compile date
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Carlos Sobrinho <duckman at epilog dot ath dot cx>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Fri, 7 Jan 2005 10:37:17 +0100
- Subject: Re: [ECOS] Access version number string of eCos to check the compile date
- References: <200501070440.45475.duckman@epilog.ath.cx>
ha On Fri, Jan 07, 2005 at 04:40:45AM +0000, Carlos Sobrinho wrote:
> Hi there, like the subject says, I would like to know how I can access the
> string with the eCos version number, 1.2/3, 2.0[b], cvs[date] and possibly
> the library compile time. Is it possible?
>
> The platform in question is a AEB1. I know its old but its a nice platform for
> a robot.
>
> I know there is a date because when I do this in install/lib dir I get:
>
> -----------------------------------------------
> $arm-elf-strings vectors.o
> - ,1
> eCos :
> Jan 7 2005
> -----------------------------------------------
>
> but how do I put it in a (diag_)printf ?
If you take a look at packages/hal/arm/arch/current/src/vectors.S you
will see
//
// Identification - useful to find out when a system was configured
_eCos_id:
.asciz "eCos : " __DATE__
However, it does not appear to be a global symbol. So actually
accessing it from another file will be difficult.
What you might want to do is
diag_printf(__DATA__);
Getting the version string is hard. Most versions of eCos don't have a
version, they are just the "current" anoncvs.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss