Message-ID: <3ADBF7A0.F7B533F5@falconsoft.be> Date: Tue, 17 Apr 2001 09:58:24 +0200 From: Tim Van Holder Organization: Falcon Software NV X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en, nl-BE, nl MIME-Version: 1.0 Newsgroups: comp.os.msdos.djgpp Subject: Re: Using MASM generated COFF files with GPP (solution) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 25 NNTP-Posting-Host: 194.78.64.238 X-Trace: 987494391 reader1.news.skynet.be 20619 194.78.64.238 X-Complaints-To: abuse AT skynet DOT be To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote: > > On Mon, 16 Apr 2001, Tom Hunt wrote: > > > say we're writing a function foo and assembling it with MASM using the > > command line > > ml /c /coff foo.asm > > "ml"? Isn't the name of the MASM executable masm.exe? > > Thanks for the rest of the info, I'll probably put it into the next > release of the DJGPP FAQ. It's a bit (though only a bit) like saying 'Isn't the name of the GNU C Compiler cc1plus.exe?'. As I understand it, ml is the compiler/linker driver. The /c option tells it to compile, not link. It's also the standard command used by NMAKE for .asm files, I think (not sure though). -- Tim Van Holder - Falcon Software N.V. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This message was posted using plain text. I do not endorse any products or services that may be hyperlinked to this message.