From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31161 invoked by alias); 5 Oct 2010 21:51:49 -0000 Received: (qmail 31141 invoked by uid 22791); 5 Oct 2010 21:51:48 -0000 X-SWARE-Spam-Status: No, hits=-50.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from mail-ww0-f45.google.com (HELO mail-ww0-f45.google.com) (74.125.82.45) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 05 Oct 2010 21:51:43 +0000 Received: by wwa36 with SMTP id 36so7406780wwa.2 for ; Tue, 05 Oct 2010 14:51:40 -0700 (PDT) Received: by 10.227.127.149 with SMTP id g21mr9428765wbs.218.1286315500677; Tue, 05 Oct 2010 14:51:40 -0700 (PDT) Received: from [127.0.0.1] (S0106000cf16f58b1.wp.shawcable.net [24.76.240.202]) by mx.google.com with ESMTPS id x33sm42900weq.23.2010.10.05.14.51.38 (version=SSLv3 cipher=RC4-MD5); Tue, 05 Oct 2010 14:51:39 -0700 (PDT) Subject: Re: trouble posting to cygwin-apps From: "Yaakov (Cygwin/X)" To: cygwin In-Reply-To: <4CAB98BF.8050006@kitware.com> References: <4CAA3A16.1000103@kitware.com> <4CAB8EA9.8020104@cwilson.fastmail.fm> <4CAB98BF.8050006@kitware.com> Content-Type: text/plain; charset="UTF-8" Date: Tue, 05 Oct 2010 21:51:00 -0000 Message-ID: <1286315505.8828.334.camel@YAAKOV04> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2010-10/txt/msg00098.txt.bz2 On Tue, 2010-10-05 at 17:29 -0400, Bill Hoffman wrote: > On 10/5/2010 4:46 PM, Charles Wilson wrote: > > Will this include fixes for WIN32 being erroneously defined for cygwin? > > http://cmake.org/Bug/view.php?id=10122 > > > > This just bit me trying to build opencv; no, I don't want > > window_w32.cpp cvcap_vfw.cpp cvcap_cmu.cpp > > cvcap_w32.cpp cvcap_dshow.cpp > > added to my cygwin build of opencv, since doing so breaks the build... > > No, it will not. I don't think all of those issues have even been > resolved in the development branch of CMake due to backwards > compatibility concerns. However, this is more of a discussion for the > CMake developer mailing list. Bill, As you are aware, my CMake build in Ports contains the necessary patches. We (Cygwin package managers) need WIN32 to be undefined for software to build in a *NIX/X11 mode on Cygwin, and we are not concerned with backwards compatibility with what we perceive to be incorrect behaviour. Without these changes, many of us will still need to rely on Ports' CMake, continuing the conflicts between Ports and the distro which I am trying to eliminate. Secondly, Qt4 has been available for some time, so cmake-gui can now be provided. Due to the substantial additional dependencies of Qt, this should be a separate binary package; my .cygport shows how this can be done. My patches for 2.8.2 are available here: http://cygwin-ports.git.sourceforge.net/git/gitweb.cgi?p=cygwin-ports/ports;a=tree;f=devel/cmake Regardless of the current upstream state, I must ask you to include these patches for our distribution so that your cmake packages will be useful to us in the meantime, until we can find a mutually agreeable solution. Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple