Subject:
|
Re: NQC default output file
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Thu, 13 Jan 2000 21:13:06 GMT
|
Reply-To:
|
MATTDM@MATTDM.spamcakeORG
|
Viewed:
|
1412 times
|
| |
|
|
Joel Shafer <joel@shafersystems.com> wrote:
> 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 & object code in another directory with r/w permissions.
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 is a good example).
One argument would be: cc puts the default a.out in the current
directory. In fact, is there an example of the program which does it like
nqc?
I realize that this is minor and pedantic, as the -O option can be used to
make it go anywhere. But I was confused.
--
Matthew Miller ---> mattdm@mattdm.org
NQC RPMs (i386 and source) ---> http://www.mattdm.org/mindstorms/nqc/
Quotes 'R' Us ---> http://quotes-r-us.org/
|
|
Message is in Reply To:
 | | Re: NQC default output file
|
| 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 & (...) (24 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
5 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
