 | | Re: 0.2.1 API
|
|
Never mind- did it myself. Thanks anyway... -Luis (...) ###...### Profanity is the one language that all programmers understand. -Anonymous ###...### (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | 0.2.1 API
|
|
I seem to remember that someone here installed doxygen and generated a new set of API docs for 0.2.0. Am I correct in that? Or am I smoking something? If that is the case, I'd love to hear from you- a copy would be real nice to re-link from the (...) (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | rcx tools setup
|
|
I have following problem with setting up the rcx tools (the old ones, distributed with legOS-0.1.7): I set up the Makefile.common to properly point to my paths: TOOLPREFIX=/home/eri...tachi-hms- LEGOS_ROOT=/home/eri...gOS-0.1.7/ when I run make I (...) (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: RCX-enhanced egcs
|
|
I just downloaded the new rcx tools, unfotunately the gcc dies (segmentation fault, even if I run the gcc only (with no parameters). any ideas what's going on? does it require glibc2.1? any settings? TIA erik (...) (25 years ago, 4-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | IR
|
|
Hi All. Is there a way to set the IR transmitter to something like 'long range mode'? I would like to have a more powerful beam for proximity detection. I've tried lnp_logical_range(1), doesn't seem to make a difference. The problem is that I don't (...) (25 years ago, 2-Nov-99, to lugnet.robotics.rcx.legos)
|
| |
| | Re: legOS-0.2.1
|
|
Hi Jeffrey, that's an OS issue - your host system should define O_ASYNC. Some older systems define FASYNC instead, try that one. You can work around this more elegantly, too: #ifndef O_ASYNC #define O_ASYNC FASYNC #endif And hope for the best. (...) (25 years ago, 2-Nov-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx)
|
| |
| | Re: legOS-0.2.1
|
|
(...) ==bulk of message removed (...) I'm getting a compile error when building the dll utility - an undefined symbol 'O_ASYNC' forgive my ignorance but how do I fix this? Thanks in advance, -=RoboCoder=- (25 years ago, 1-Nov-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx)
|
| |
| | Re: fast firmware downloader
|
|
I hate to admit it, but the version of Turbo C++ I just pulled out is 1.00. I departed from the Borland compiler shortly after acquiring this version and did not keep up with advances. Would I gain any advantages by finding a later version, or (...) (25 years ago, 31-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
| |
| | RE: fast firmware downloader
|
|
(...) Yeah. Not sure about the hardware interface, though. Would it be possible to run the DOS executable to generate a binary and then download it otherwise? I too am not sure what this whole discussion is about- if it is just NQC, then it is (...) (25 years ago, 30-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
| |
| | RE: fast firmware downloader
|
|
(...) Wes and Dave, I pulled out an ancient copy of Turbo C++ 3.0 for DOS. It compiles most of the code but chokes on the >8 character file names. I might have to try Microsoft VC++ next....to make a DOS executable. I also found a DOS C Comm library (...) (25 years ago, 30-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
