Subject:
|
Re: HELP - LegOS for Windows
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Thu, 3 Feb 2000 00:02:50 GMT
|
Viewed:
|
2749 times
|
| |
|
|
"Rossz Vámos-Wentworth" <rossw@jps.net> wrote in message
news:38989DC8.62ED27FC@jps.net...
> alex wetmore wrote:
> > Why are you using the 16-bit (DOS) DJGPP tools under Windows NT instead • of
> > the Cygwin 32-bit stuff? You won't run into any of these command line
> > length headaches when using the 32-bit shell and tools.
>
> The DJGPP tools are 32-bit. It's a limitation of the DOS shell • (COMMAND.COM &
> CMD.EXE) that is the problem.
The problems that you are mentioning generally only occur after running
16-bit programs (and thus ending up with a 16-bit shell). The cmd.exe is
not a DOS shell and has no problem with long command lines or long file
names. You can prove this to yourself by firing up command and echoing a
long command:
C:\Documents and Settings\awetmore>echo
1234567890123456789012345678901234567890
1234567890123456789012345678901234567890123456789012345678901234567890123456
7890
1234567890123456789012345678901234567890123456789012345678901234567890
1234567890123456789012345678901234567890123456789012345678901234567890123456
7890
1234567890123456789012345678901234567890123456789012345678901234567890123456
7890
123456789012345678901234567890
(that is 200 characters).
If I drop into the command.com (by typing command.com) then I end up with a
maximum command line length of 127 characters. This is a DOS limitation,
and command.com is running in the DOS emulator. There is really no reason
to run command.com on an NT machine unless you need to run some legacy DOS
programs. If your build environment is truly 32-bit (as you are saying)
then this is not necessary at all.
> Cygwin doesn't have a command line limit problem, but it has its own • unique
> headaches. Read the number of posts of people trying to get the Cygwin • system
> working for legOS development to get an idea of what a pain it can be for
> non-Unix people.
I got cygwin/LegOS working on my Windows 2000 box. It was a hassle, but the
hassles were related to LegOS, not Cygwin. The patches necessary to make
LegOS were hard to find, and some of the patches that I found didn't work.
I ended up having to do a lot of hand patching to get things operating.
The cygwin tools worked just fine, and I haven't had any problems with
command line lengths.
I agree that setting up LegOS on Win32 is a pain, but I don't think that
Cygwin is the cause of the pain.
alex
|
|
Message is in Reply To:
 | | Re: HELP - LegOS for Windows
|
| (...) The DJGPP tools are 32-bit. It's a limitation of the DOS shell (COMMAND.COM & CMD.EXE) that is the problem. Cygwin doesn't have a command line limit problem, but it has its own unique headaches. Read the number of posts of people trying to get (...) (25 years ago, 2-Feb-00, to lugnet.robotics.rcx.legos)
|
15 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
