On Mon, 10 Nov 2014 13:29:02 +0000 Solomon E via Digitalmars-d-learn <digitalmars-d-learn@puremagic.com> wrote:
> The problem that I'm having with this seems to be with GDC, not > the rest of the D community. The following is a quote of the > entire amount of information in the GDC man page on the following > compiler options and file extensions: > > SYNOPSIS > gdc [-c] > [-g] [-pg] [-Olevel] > [-Idir...] [-Ldir...] > [-o outfile] infile... > > For any given input file, the file name suffix determines > what kind of > compilation is done: > > file.d > D source files. > > file.di > D interface files. > > file.o > Object files to link in. > > file.a > Library files to link in > > > So I could *guess* that a dot o file is the equivalent of a .obj > file an Windows, and *guess* that a dot a file is the equivalent > of a .lib file on Windows, then follow some Windows instructions > as on the page > http://wiki.dlang.org/Compiling_and_linking_with_DMD_on_Windows > but I would totally be guessing, and I still wouldn't know where > to get any .a files, but I could *guess* that I would get a .o > file by running the compiler and naming the output a .o file by > using the -o switch. I would be totally guessing, and if I'm > wrong, all my builds would be wrong and incompatible with other > people's build systems. you'd better use some IDE if you have to guess such things. gdc manpage documents gdc-specific options. it even gives you some directions in "see also" section, which you are supposed to follow to read more about GCC suite. GCC also has extensive on-line documentation. yes, you are supposed to know how to use GCC, part of which gdc is. if you don't want to think about that, you can use IDE which does all this for you automatically.
signature.asc
Description: PGP signature
