|
|
 | | 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 (...) (26 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 (...) (26 years ago, 30-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
| | | | | RE: fast firmware downloader
|
| (...) I tried to do a DJGPP build of binutils and it didn't work for me. I really didn't want to spend more time futzing with the tools, and I was already using Cygwin, so I used one of the precompiled toolsets. I think you are just a lazy typer, (...) (26 years ago, 30-Oct-99, to lugnet.robotics.rcx)
| | | | | Re: fast firmware downloader
|
| (...) Actually, lots of packages try to deal with filenames intelligently. QT, for example, has normal C++ NamingConventions, but uses lowercaseonly file names. I try to do the same. Notice how direct-sensor.h became dsensor.h in 0.2.0, as well as (...) (26 years ago, 30-Oct-99, to lugnet.robotics.rcx)
| | | | | 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 (...) (26 years ago, 30-Oct-99, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx, lugnet.robotics.rcx.pbforth)
|
|
