 | | NQC default output file —Matthew Miller
|
| | | I was checking to see if NQC already does have an option to spit bytecodes to stdout (-L would work, if rcxcomm would understand the format) and I came across something that seems nonintuitive to me. The default output file is "named the same as the (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| | | |
| | | | | Re: NQC default output file —Joel Shafer
|
| | | | | I don't think it's nonintuitive. I think it makes sense to have the output go to the same directory as the input. That way you can have a directory set up for the executable with only read/execute permissions, and yet have all of your source & (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| | | | | |
| | | | | | | Re: NQC default output file —Matthew Miller
|
| | | | | | (...) I don't want the outfile to go where the executable is -- I want it to go to the current working directory. So nqc goes in /usr/local/bin, and I can run it from "binaries" directory on source files that might be located elsewhere (the test.nqc (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| | | | | | |
| | | | | Re: NQC default output file —Dave Baum
|
| | | | (...) I just added the error check to nqc. I haven't changed the directory yet, though. Using the source directory was strictly from laziness. Assuming there aren't massive objections, I'll switch to using the current directory. Dave Baum (25 years ago, 15-Jan-00, to lugnet.robotics.rcx.nqc)
|
| | | | |
| | | | | | Re: NQC default output file —Matthew Miller
|
| | | | (...) Cool, thanks. (25 years ago, 19-Jan-00, to lugnet.robotics.rcx.nqc)
|
| | | | |
