 | | Re: Current Makefile logic fails for nonNT Windows OS
|
|
Taking a second look at this and noticing some past post about this issue with WinXP ((URL) a much cleaner code might look like the following # # WindowsNT/Cygnwin, test against several values: # ifneq (,$(findstring $(OSTYPE),cygwin32 cygwin (...) (22 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| |
| | Current Makefile logic fails for nonNT Windows OS
|
|
I am compiling under windows 98 using cygwin version 1.3.10. In Makefile.common (/legOS-0.2.6,/legOS....2.6/util) the logic to determine whether the OS is a windows system fails due to the fact that uname returns CYGWIN_98-4.10. I submitted a bug (...) (22 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| |
| | Accurate msleep and timeslicing - was Re: sys_timer
|
|
"Michael Obenland" <obenland@t-online.de> wrote in message news:GvJ5vD.7MC@lugnet.com... <snip> (...) switch. (...) I made some modifications to the tm_sleep_wakeup that allows high priority tasks to wake up at exactly the time specified for msleep (...) (22 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: sys_timer
|
|
(...) Yes. (...) That is right. (...) It does, actually. The timer itself counts the millisec. But if you do a wait_event() call, your running program gives up its time slice, the OS waits for the event and then continues your task with the next (...) (22 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
| |
| | sys_timer
|
|
I recently adopted legOS as my development environment and I have to say I tremendously impressed. Thanks to everyone who has worked so hard on it. It is really a first class, grade A product. Is sys_timer accurate to within 1 ms? unsigned long (...) (22 years ago, 3-May-02, to lugnet.robotics.rcx.legos)
|
