RTEMS Scheduler Simulator Status Update

[Joel Sherrill]

Using The Scheduler Simulator is now in AsciiDoc and in the
the rtems-schedsim/schedim directory. It should be easier to
fix and update now.

Chris.. can you provide the asciidoc command that generates
the spiffy rtems source builder page. :)

On 5/5/2013 10:55 AM, Joel Sherrill wrote:
> On 5/5/2013 8:30 AM, wei.a.yang wrote:
>>
>> 在 2013-5-4，22:01，Joel Sherrill <joel.sherrill at oarcorp.com 
>> <mailto:joel.sherrill at oarcorp.com>> 写道：
>>
>>> On 5/3/2013 9:18 PM, yangwei weiyang wrote:
>>>> Hi
>>>>
>>>> When i build the scheduler-sim it encountered some error:
>>>>
>>>> weiy at WeiY-host:/project/weiy/gsoc2013/rtems-schedsim$ autoconf
>>>> configure.ac:18 <http://configure.ac:18>: error: possibly undefined 
>>>> macro: AM_INIT_AUTOMAKE
>>>>       If this token and others are legitimate, please use 
>>>> m4_pattern_allow.
>>>>       See the Autoconf documentation.
>>>> configure.ac:19 <http://configure.ac:19>: error: possibly undefined 
>>>> macro: AM_MAINTAINER_MODE
>>>>
>>>
>>> You need to run the bootstrap script found at the top of the main
>>> RTEMS source tree.
>>>
>>> rtems-schedsim avoids duplicating files from the main source tree.
>>>
>>> Can you build the RTEMS head? rtems-schedsim uses the same version
>>> of autoconf and automake.
>> Thank you Joel, I have built the sim successfully and run all the 
>> scenarios. So next step I will look deep into its source code and 
>> learn how to write test scenarios.
>>
> Great! I didn't think it was hard to build. :)
>
> I have attached two Open Office Documents which I wrote when the simulator
> was created. There is a README in rtems-schedsim/schedsim which 
> unfortunately
> looked to be corrupted by the cvs->git transition. It should be a 
> subset of what
> is in these documents.
>
> I think I will convert at least the Using document to asciidoc and 
> replace the
> README. :)
>
>
>
>>>> Is there any reference about how to configure and build the schedsim.
>>>>
>>>>
>>> There is a readme at the top of the source tree.
>>>>
>>>>
>>>> 2013/5/2 Joel Sherrill <joel.sherrill at oarcorp.com 
>>>> <mailto:joel.sherrill at oarcorp.com>>
>>>>
>>>>     Hi
>>>>
>>>>     I just wanted to pass along that the RTEMS Scheduler
>>>>     Simulator is now updated and appears to be working
>>>>     great with the current RTEMS source. The git is:
>>>>
>>>>     git://git.rtems.org/rtems-schedsim.git
>>>>     <http://git.rtems.org/rtems-schedsim.git>
>>>>
>>>>     I also updated the wiki page:
>>>>
>>>>     http://wiki.rtems.org/wiki/index.php/SuperCore_Scheduler#Scheduler_Simulator
>>>>
>>>>     This should be of use to at least two GSOC proposals.
>>>>
>>>>     -- 
>>>>     Joel Sherrill, Ph.D.             Director of Research & Development
>>>>     joel.sherrill at OARcorp.com        On-Line Applications Research
>>>>     Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>>>>     Support Available                (256) 722-9985
>>>>
>>>>     _______________________________________________
>>>>     rtems-devel mailing list
>>>>     rtems-devel at rtems.org <mailto:rtems-devel at rtems.org>
>>>>     http://www.rtems.org/mailman/listinfo/rtems-devel
>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>> Wei Yang
>>>> Best Regards
>>>>
>>>> wei.a.yang at gmail.com <http://gmail.com>
>>>>
>>>
>>>
>>> -- 
>>> Joel Sherrill, Ph.D.             Director of Research & Development
>>> joel.sherrill at OARcorp.com         On-Line Applications Research
>>> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>>> Support Available                (256) 722-9985
>
>
> -- 
> Joel Sherrill, Ph.D.             Director of Research & Development
> joel.sherrill at OARcorp.com         On-Line Applications Research
> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
> Support Available                (256) 722-9985


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20130505/c3e3b8c2/attachment-0001.html>