Re: [ECOS] EXEEXT settable in generated buildtree, via CDL ??

[sandeep <shimple0 at yahoo dot com>]

> The idea of having suffixes for test executables was
> considered very briefly in the early days of the
eCos
> design, and rejected. They are more trouble than
they
> are worth.
bart, can you please indicate the what you meant by
troubles in this case? in short can you please mention
the troubles and also what you consider the worth of
these. 

> Of course if an application developer wants to use
> some kind of suffix for executables, that is fine.
> eCos does not mandate how applications get built.
true. the regression suite i have made, based on
developers' initial days experience with testing
process, works with any extension/ no extension, as
user configures it, but for one assumption that root
of directory tree user supplies as one containing
tests, follows the layout of buildroot/install/tests/
. so it is not a developer's issue, for them even
solutions in initial post, work fine.

the root cause is the need of PM/Advisor to ecos team,
 the gui tool used for loading and running the tests
lists the files with a particular extension by
default, so he has to click on "show all files". since
the ways mentioned in initial post to get the desired
extension are not user friendly for his needs, he
wanted to have extension specified as a part of
configuration.

since you plan to omit EXEEXT in future and you will
be sharing the troubles with EXEExT, after that i can
decide how much worth is spending time in this stuff
as compared to other important issues.

sandeep



		
__________________________________ 
Do you Yahoo!? 
Take Yahoo! Mail with you! Get it on your mobile phone. 
http://mobile.yahoo.com/maildemo 

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss