public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Tony Kelman <tony@kelman.net>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITA] cmake 3.12.0
Date: Thu, 26 Jul 2018 19:05:00 -0000	[thread overview]
Message-ID: <MWHPR22MB06869A15BA725D0735DCF3DDA72B0@MWHPR22MB0686.namprd22.prod.outlook.com> (raw)
In-Reply-To: <59df30e9-347f-d75d-66a1-c9357b9ef442@gmail.com>

> do you need a static lib ?
> I saw some distri are packaging it.

Presumably the static lib should go in a -devel package? I wouldn't
want to link cmake to the static lib though, that would defeat the
purpose of de-vendoring it and using separately packaged dependencies.

> builds successfully out of box for Cygwin with default build
> script provided by Kitware.

The default build script uses vendored dependencies which is
understandable for Kitware's own reproducibility and testing burden,
but generally not the way distros prefer to build cmake. Better to
follow the example of the way the existing package is built, but
updating the patches and accounting for new dependencies.

  parent reply	other threads:[~2018-07-26 19:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 14:16 Ivan Shynkarenka
2018-07-24 14:18 ` Ivan Shynkarenka
2018-07-24 14:48   ` Marco Atzeri
2018-07-24 14:47 ` Takashi Yano
2018-07-24 19:01 ` Achim Gratz
2018-07-24 20:05   ` cyg Simple
2018-07-24 20:50     ` Achim Gratz
2018-07-24 20:56       ` Ivan Shynkarenka
2018-07-25  6:44       ` Marco Atzeri
2018-07-26  0:50         ` Tony Kelman
2018-07-26  6:00           ` Marco Atzeri
2018-07-26  7:07             ` Marco Atzeri
2018-07-26  9:28               ` Ivan Shynkarenka
2018-07-26 19:05               ` Tony Kelman [this message]
2018-07-26 18:41             ` Achim Gratz
2018-07-26 19:33               ` Marco Atzeri

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=MWHPR22MB06869A15BA725D0735DCF3DDA72B0@MWHPR22MB0686.namprd22.prod.outlook.com \
    --to=tony@kelman.net \
    --cc=cygwin-apps@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).