Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Gerald S. Williams" To: "Jason Tishler" Cc: Subject: RE: "Best" way to build a DLL? Date: Fri, 15 Feb 2002 15:52:28 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <20020215203224.GO600@hp.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Thanks for the nudge. After seeing your mail, I poked around pyconfig.h and found the USE_DL_IMPORT define. Anyway, if you're linking to Cygwin Python, -DUSE_DL_IMPORT on the gcc line eliminates those informational "Warnings", at least from the Python library. Presumably, the distutils package sets this automatically, but we're not using it. -Jerry -O Gerald S. Williams, 22Y-103GA : mailto:gsw@agere.com O- -O AGERE SYSTEMS, 555 UNION BLVD : office:610-712-8661 O- -O ALLENTOWN, PA, USA 18109-3286 : mobile:908-672-7592 O- Jason Tishler wrote: > Just to be clear, I'm building Cygwin Python the way that I always have > (at least since my shared extension patch was accepted). I assume you > meant that I *could* build without __declspec() declarations if I desired. > Since the __declspec's are there for Win32, I might as well use them. -- 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/