[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: howto handle targets I can't execute
From: |
Dave Korn |
Subject: |
RE: howto handle targets I can't execute |
Date: |
Wed, 13 Feb 2008 17:52:48 -0000 |
On 13 February 2008 16:05, Joel Sherrill wrote:
> On to the next matter. I can only run tests automatically
> for a handful of the RTEMS targets. I am working to
> expand that set but it is always going to be an issue.
>
> What's the proper way to handle a target I don't have
> a simulator or target hardware for? Is there a standard
> way to just go through the build sequence, not even
> attempt to run anything and still report the results
> in way that is meaningful?
Yes, you can build a cross-targeted compiler and should at least get sane
results for e.g. the compile tests, only the execute tests actually require a
real target.
You could always compile "int main() { abort (); }" and supply it as a
stand-in for a real simulator if there's a hole in the framework needs
plugging :-)
cheers,
DaveK
--
Can't think of a witty .sigline today....