Subject:
|
Re: NQC 2.1 b2 in beta test
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Fri, 14 Jan 2000 17:06:53 GMT
|
Viewed:
|
1591 times
|
| |
|
|
Dave Baum wrote:
> > The beta does not seem to work with RcxCC. All it does is display the
> > parameters for NQC and then exits. No compile.
>
> Hmmm - the only reason I can think of for this would be if RcxCC is using
> one of the deprecated options that were removed in 2.1 (-o, -e, and -s
> which were replaced by -O, -E, and -S). If Mark can confirm which ...
The same problem was already present with the b1 (I had asked about it in this
newsgroup but got no reply).
Also, I don't think it is related to the parameters. I have now checked the exec
call of RcxCC with a debugger and found this is the command line it sends:
nqc -E"temp.log" -L"temp.lst" -I"C:\NQC\CC\" temp.nqc
As far as I can see, nothing wrong with it, is it?
Uwe
|
|
Message has 1 Reply:
 | | Re: NQC 2.1 b2 in beta test
|
| (...) the exec (...) The answer isn't pretty.... As near as I can tell (sorry, not much of a Windows expert), the command line gets passed in its entirety to the executable, which then is responsible for parsing it into separate arguments. For the (...) (25 years ago, 15-Jan-00, to lugnet.robotics.rcx.nqc)
|
Message is in Reply To:
| | Re: NQC 2.1 b2 in beta test
|
| (...) Hmmm - the only reason I can think of for this would be if RcxCC is using one of the deprecated options that were removed in 2.1 (-o, -e, and -s which were replaced by -O, -E, and -S). If Mark can confirm which (if any) of these options are (...) (25 years ago, 14-Jan-00, to lugnet.robotics.rcx.nqc)
|
25 Messages in This Thread:
 
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
