public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin <cygwin@cygwin.com>
Subject: Re: trouble posting to cygwin-apps
Date: Tue, 05 Oct 2010 21:51:00 -0000	[thread overview]
Message-ID: <1286315505.8828.334.camel@YAAKOV04> (raw)
In-Reply-To: <4CAB98BF.8050006@kitware.com>

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

  parent reply	other threads:[~2010-10-05 21:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 20:33 Bill Hoffman
2010-10-05  8:07 ` Corinna Vinschen
2010-10-05 12:29   ` Bill Hoffman
2010-10-05 15:32     ` Corinna Vinschen
2010-10-05 20:46 ` Charles Wilson
2010-10-05 21:29   ` Bill Hoffman
2010-10-05 21:47     ` Marco Atzeri
2010-10-05 21:51     ` Yaakov (Cygwin/X) [this message]
2010-10-05 22:13       ` Bill Hoffman
2010-10-07  6:21         ` Yaakov (Cygwin/X)
2010-10-07 12:54           ` Bill Hoffman
2010-10-05 22:31   ` OpenCV: (Re: trouble posting to cygwin-apps) Yaakov (Cygwin/X)
2010-10-06  3:34     ` Charles Wilson
2010-10-07 21:45 ` trouble posting to cygwin-apps Christopher Faylor
2010-10-07 21:57 Gregg Levine
2010-10-07 22:16 ` Christopher Faylor
2010-10-08 13:05   ` Bill Hoffman
2010-10-08  6:20 SZABÓ Gergely
2010-10-08 13:52 ` Eric Blake
2010-10-08 15:41 ` Christopher Faylor
2010-10-08 19:27 ` Kenneth Wolcott
2010-10-11  8:01   ` Csaba Raduly
2010-10-11  8:12     ` SZABO Gergely
2010-10-08 14:20 SZABO Gergely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1286315505.8828.334.camel@YAAKOV04 \
    --to=yselkowitz@users.sourceforge.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).