Message-Id: <199908061124.OAA29550@ankara.Foo.COM>
From: "S. M. Halloran" <mitch AT duzen DOT com DOT tr>
Organization: User RFC 822- and 1123-compliant
To: djgpp AT delorie DOT com
Date: Fri, 6 Aug 1999 15:29:39 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: OBJ files with DJGPP
In-reply-to: <7obg87$bih$1@taliesin.netcom.net.uk>
X-mailer: Pegasus Mail for Win32 (v3.11)
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 5 Aug 99, Michael Stewart was found to have commented thusly:

> Travis wrote in message <37A8E3E3 DOT A21CAD9D AT hotmail DOT com>...
> >How do I get djgpp to produce microsoft and borland compatable object
> >files (.OBJ)?
> 
> 
> I don't think you can.

Really?

What about this?  Assuming the poster has C/C++ source code and doesn't have 
the commerical compilers mentioned above:

1. Compile with gcc using the -S option to get the assembler output.  Note that 
gcc produces the assembler code in AT&T/Unix style, not in the Intel style.

2. There are utilities discussed in DJGPP FAQ that allow you to convert 
assembler from AT&T<--->Intel style.  (apparently in both ways, using different 
utilities).  See in particular the very last paragragh of FAQ 17.2

3. Since the AT&T-->Intel converter mentioned above has apparently been 
optimized to work with the Netwide Assembler (NASM), which is the assembler I 
was going to recommend and will produce object files in apparently many formats 
(COFF, OBJ, etc), you then just produce your object with NASM, and cross your 
fingers.

You should know I have never tried these steps, but then I haven't had the need 
for .OBJ files either.

Mitch Halloran
Research (Bio)chemist
Duzen Laboratories Group
Ankara       TURKEY