The Place to Start for Operating System Developers
https://f.osdev.org/
hum ... straight from "man gcc" ...OSMAN wrote: $ gcc -c hello.c
produce hello.exe as they say at mingw.org?
I don't think so; it's a.out.
and a bit later ...-c Compile or assemble the source files, but do not link.
The linking stage simply is not done. The ultimate
output is in the form of an object file for each
source file.
By default, the object file name for a source file is
made by replacing the suffix .c, .i, .s, etc., with
.o.
These are both detailed into "overall options" ...-o file
Place output in file file. This applies regardless to
whatever sort of output is being produced, whether it
be an executable file, an object file, an assembler
file or preprocessed C code.
Since only one output file can be specified, it does
not make sense to use -o when compiling more than one
input file, unless you are producing an executable
file as output.
If -o is not specified, the default is to put an exe?
cutable file in a.out, the object file for source.suf?
fix in source.o, its assembler file in source.s, and
all preprocessed C source on standard output.
Code: Select all
cross-compiled-gcc -Wall -g -o hello.exe hello.c