Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: kulack AT us DOT ibm DOT com X-Lotus-FromDomain: IBMUS To: "Tim Prince" cc: "Jean-Luc Vay" , cygwin AT sourceware DOT cygnus DOT com Message-ID: <85256915.0077E1E6.00@D51MTA04.pok.ibm.com> Date: Fri, 7 Jul 2000 16:49:32 -0500 Subject: Re: linking windows dll with cygwin gcc Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sorry, I don't know anything about the product you're using, but this may work for you. Support has been added for direct use of MS .lib files for your imports (I suspect your product probably has those). Example: > make cli1.exe gcc -g -mthreads -I. -I/db2src/test -I/sqllib/include cli1.c /SQLLIB/lib/db2api.lib /SQLLIB/lib/db2apie.lib /SQLLIB/lib/db2cli.lib /db2src/test/libxa.a /db2src/test/libtps.a mv a.exe cli1.exe I've been using this and having really good luck. GCC version: gcc-2.95.2-2.tar.gz I got an interesting exception in one certain circumstance when I added a new function from a different DLL but I couldn't track it down and worked around it in some other fashion. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com