[Issue 18710] executable file not generated when -o- is used

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=18710

Mike Franklin  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #3 from Mike Franklin  ---
I don't feel like dealing with such an insignificant issue.  Since I now
understand what was meant, I'm going to close this as invalid.

--

[Issue 18710] executable file not generated when -o- is used

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=18710

--- Comment #2 from Mike Franklin  ---
The "help" output currently says:

> -o-   do not write object file

I was under the assumption that that meant it would not generate the
intermediate object files when generating the executable.  I suppose this issue
could be resolved by clarifying that it doesn't generate any binary output. 
Maybe "disable object code generation", if that's what it actually does.

--

[Issue 18710] executable file not generated when -o- is used

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=18710

Seb  changed:

   What|Removed |Added

 CC||greensunn...@gmail.com

--- Comment #1 from Seb  ---
AFAIK `-o-` became the "undocumented" way to turn DMD's entire backend off.

> I think `dmd -o- main.d` should generate the `main` executable, but not the 
> `main.o` object file.

Hmm, how would you turn off object generation then?
Note that dmd -ofmain main.d won't generate an object file, but only the main
executable.

--

[Issue 18710] executable file not generated when -o- is used

[d-bugmail--- via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=18710

Mike Franklin  changed:

   What|Removed |Added

   See Also||https://issues.dlang.org/sh
   ||ow_bug.cgi?id=12116

--