Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <3BBA9D57.5050109@ece.gatech.edu> Date: Wed, 03 Oct 2001 01:08:39 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010815 X-Accept-Language: en-us MIME-Version: 1.0 To: Danny Smith CC: "Asbenson, Lyndell L" , "'cygwin@cygwin.com'" Subject: Re: DLL Win 2000 References: <20011003044928.77310.qmail@web14505.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Danny Smith wrote: > --- Charles Wilson wrote: > > > > >>The problem is, MS .obj format files are NOT compatible with gcc/ld. >>I'm really surprised you were able to link at all. >> >> > > This is news to me. As long as the obj file has no dependency on static > MS runtime (or other MS static lib), on MS debug heap or on C++ > references they work, with mingw or with -mno-cygwin option. The other > gotcha is struct layout, which can be fixed with -fnative-struct > option. Ding! > > The usual problem however is dependency on MS libc[mt].lib > And another ding! What you're saying is, that *theoretically* you can use a .obj file with gcc .o's -- but in practice it's rarely possible. (1) you have to be careful to use -fnative-struct with your gcc compiliation, (2) only .obj files that make NO references to ANY runtime functions (open, fopen, printf, etc) are usable. That's a lot of restrictions. Wouldn't it be nice if the gpib IO card manufacturer released their @#$@!& source, instead of distributing .obj files? --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/