delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/02/26/14:03:10

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Mailer: exmh version 2.1.1 10/15/1999 (debian)
To: cygwin AT cygwin DOT com
Subject: MSVC++ compatible import library - HOW?
Mime-Version: 1.0
Date: Tue, 26 Feb 2002 23:59:41 +0500
From: Victor Porton <porton AT narod DOT ru>
Message-Id: <E16fmpC-0000fe-00.porton-narod-ru@home.porton.narod.ru>

Hello;

I already asked this question but my e-mail does not appears to appear in the list :-(

Is it possible to create an import library compatible with MSVC++ without MSVC++? (1. To not buy its license; 2. To not workaround its bugs.)

Microsoft's linker says something about multiple .text sections and the produced executable crashes. (Note that I link the DLL from _several_ .o files, however the source of only one of these .o files has __declspec(dllexport) directives.)

HEEELPPP!!

P.S. Borland's implib.exe also produces import libraries incompatible with MSVC++ :-(
-- 
Victor Porton (porton AT narod DOT ru)


--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019