[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

configure command line in installed directories?



On Mon, 2008-04-14 at 09:08 -0500, Joel Sherrill wrote:
> I can't believe that I can going to argue both sides of
> this one but please read the entire message. :-D
> 
> Thomas Doerfler wrote:
> > Ralf,
> >
> > maybe I need to clarify my initial request a bit:
> >
> > With my request I only want to "document" to explicitly selected
> > configure options, not the ones implicilty choosen and/or passed through
> > the source code directory hirarchy.
> >   
> We often ask "how did you configure RTEMS?" as part of
> answering a question.  Having some way to get this information
> from an installed RTEMS environment (not just RTEMS itself)
> doesn't seem like a bad idea from a support view.
It is - It is a crack-ridden idea.

You guys are lumping together packaging and configuration.


> We could have a program/script that
> queried the RTEMS environment and tools and produced
> a report including host OS, tool versions, RTEMS options,
> etc.
>   How this information is gathered could be flexible.
> A simple native C program COULD safely include the RTEMS
> cpuopts.h and bspopts.h if it didn't include anything else.
> 
> Ralf.. didn't you used to send a script out for cygwin problems?

____ configuration _____!!!!!!!!!

what Thomas is talking about is system-integration, or one step further
packaging.



Ralf