Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Date: Tue, 30 Nov 1999 14:04:33 +0200 From: Paul Sokolovsky X-Mailer: The Bat! (v1.32) S/N 34D3AC61 Reply-To: Paul Sokolovsky X-Priority: 3 (Normal) Message-ID: <14586.991130@is.lg.ua> To: "Mike White" CC: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Multiple .dll refs from one .a? (libvfw32) In-reply-To: <19991130042854.20685.qmail@hotmail.com> References: <19991130042854 DOT 20685 DOT qmail AT hotmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Mike, Mike White wrote: MW> Has anyone actually successfully run a program that MW> links with cygwin's libvfw32.a (that's Video for MW> Windows)? Specifically, the VFW32.LIB from MS's MW> Win32 SDK actually refers to functions available in MW> 3 separate .DLL's, none of which is actually named MW> VFW32.DLL. So linking works fine, but when run, MW> my program (a port from MSVC) complains that it can't MW> find VFW32.DLL. (In fact, no such .DLL exists afaik). MW> The 3 actual .DLL's are MSVFW32.DLL, AVIFIL32.DLL, MW> and AVICAP32.DLL. You confirmed suspection I had about that. It seems that some of implibs provided with gnu-win32 distributions are not functional. One reason is that they are built simple-minded, e.g. lib.a refers to .dll, which sometimes not true. You showd one example, I may rememember libth32.a for ToolHelp32 package which tries to import functions from some th32.dll which I never saw on any win9x system, while those functions live in kernel32.dll . MW> Anyhow, I think I should be able to just link against MW> the separate .a files. But, is there any way to MW> actually make a working file that does what MW> libvfw32.a "wants" to do? But you set question about possibility to have one implib for several dlls. IMHO, that's impossible with current gnuwin32 approach, or more specificall, might be possible, but require special treatment, tools for what is not available. I bet if you first create separate implibs for each dll and then merge them together, you won't get working solution. So, better have separate implib for each dll and link with them all. MW> Thanks, MW> Mike White MW> mypalmike AT hotmail DOT com Best regards, Paul mailto:paul-ml AT is DOT lg DOT ua -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com