Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <019c01c2f794$51d96f60$3778883e@pomello> From: "Max Bowsher" To: "Mader, Alexander" , "Massimiliano Mirra" Cc: References: <87pto76fcf.fsf@prism.localnet> <3E8805AA.9060000@niles.de> <87d6k75zh1.fsf@prism.localnet> Subject: Re: Building DLLs to be loaded from Visual Basic Date: Mon, 31 Mar 2003 15:46:20 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Massimiliano Mirra wrote: > "Mader, Alexander" writes: > >>> - is anybody today successfully building DLLs with cygwin (not >>> mingw32) and loading them from Visual Basic (or other languages)? >> >> I have to provide DLLs for VB and do so by using Cygwin but with >> -mnocygwin, which is more or less using mingw32. ^^^^^^^^^^ -mno-cygwin > Is that relevant to the DLL creation, i.e. do you know if a DLL built > without -mnocygwin (thus with cygwin) is still as usable? I have to > access the serial hardware on the target and I prefer to do it the > POSIX way rather than with the native API. > >> I have no idea. But I know about some problems regading VB in >> connection with C _not_ with Cygwin. So, compiling with gcc-2 it is >> usefull to use -fnative-struct (no more available/nessesary in ^^^^^^^ ^^^^^^^^^ Incorrect. Still necessary if that is what you want. Now called -mms-bitfields. >> gcc). Because of the VB- >> Structure-Conventions it could be nessesary to use -fpack-struct >> together with dummy elements in the structure in question. > > Good to know, since I built gcc2. Not even the latter is necessary in > gcc3.2, right? Still necessary. Max. -- 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/