X-Spam-Check-By: sourceware.org Date: Tue, 11 Apr 2006 10:19:21 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Cygwin backwards compatibility break with WinMain and GetCommandLine (was Re: WinMain() not getting cl...) Message-ID: <20060411141921.GA15620@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20060404184447.GA4824@tela.daveroth.dyndns.org> <20060410013414.GA20557@trixie.casa.cgf.cx> <20060410173850.GA19752@trixie.casa.cgf.cx> <443AA212.DF9AB154@dessent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Mon, Apr 10, 2006 at 02:52:04PM -0400, Igor Peshansky wrote: >On Mon, 10 Apr 2006, Brian Dessent wrote: >> Igor Peshansky wrote: >>>If GetCommandLine lives in libcygwin.a, then programs linked on older >>>versions of Cygwin will not link that function in, and thus won't work >>>with the new DLL. Programs linking with the new version of Cygwin will >>>have that function, but due to API changes, may not work with older >>>DLLs. Or am I missing something? >> >>It should work out like this: >> >>Linked against <1.5.20, Run against >=1.5.19: calls kernel32's GCL() >>and won't work >> >>Linked against <1.5.20, Run against <1.5.19: calls kernel32's GCL() but >>the win environment exists, success >> >>Linked against >=1.5.20, Run against any version: calls libcygwin's >>static GCL(), which works in any circumstance > >I'm worried about the case > >Linked against >=1.5.20, Run against <=1.5.19: calls libcygwin's static >GCL, which works, but fails because 1.5.20 (or 1.5.21, etc) has an >extra API function that now gets invoked by the code, but is missing >from 1.5.19 and earlier -- BOOM. > >IOW, the infamous "Procedure entry point ... couldn't be found" popup. So you're thinking that a program which has had no other changes, and hasn't been recompiled, is going to somehow pull in newer functions from cygwin1.dll? Please provide examples of how that could happen. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/