This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Linux Synthetic target problems


Thank you for the additional tips. Though to be honest I do not (yet) see the utility of the IO auxiliary. What we could really use is a way to input data to the application, which I do not believe is currently possible. Is this true?

Thank you,
Tyler

> -----Original Message-----
> From: Sergei Gavrikov [mailto:sergei.gavrikov@gmail.com]
> Sent: Thursday, September 04, 2008 2:39 PM
> To: Tyler Wilson
> Cc: Andrew Lunn; Bart Veer; ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] Linux Synthetic target problems
> 
> Tyler Wilson writes:
> 
> [snip]
> 
> > If this is all successful, you can then execute â./helloâ,
> > â./twothreadsâor â./simple-alarmâ to test.
> 
> You will be more expessed when run those apps with '--io' command line
> option:
> 
> ./twothreads --io
> 
> or beeing inside a fresh built directory for synth target fulfil:
> 
> make -C kernel/current TESTS=tests/tm_basic
> ./install/tests/kernel/current/tests/tm_basic --io
> 
> and yet another funny example: where is synthetic dog from?
> 
> ecosconfig new linux
> ...
> ecosconfig add watchdog
> ecosconfig tree
> make
> make -C io/watchdog/current tests
> ./install/tests/io/watchdog/current/tests/watchdog2 --io
> 
> [snip]
> 
> > When I first looked at eCos, I was not thrilled by the naming scheme,
> > and it was unclear to me how the system worked. The more I work it
> > though, the more impressed I am in the modularity and customization
> > ability of the system. Now, to build some applications...
> 
> if you noticed there is 'makefile' inside build tree (not 'Makefile'),
> so you can build own Makefile for your application or project just
> using these build_Make.params, build_Makefile are placed in examples
> directory, same lazy example:
> 
> echo 'main(){printf("howdy!\n");}' > foo.c
> SRCS=foo.c DST=foo $ECOS_REPOSITORY/../examples/build_Makefile
> make -f Makefile
> ./foo
> ^C
> 
> You see what `build_Makefile' won't overwrite eCos `makefile', but
> builds `Makefile' for your application or project.
> 
> Happy eCosing,
> 
> Sergei

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]