From: Ivan Shynkarenka <chronoxor@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] cmake 3.12.0
Date: Thu, 26 Jul 2018 09:28:00 -0000 [thread overview]
Message-ID: <CAHVoUt2PVbACqMpJGjTjArkaJKbi95zQzNL4bo45QCyumbpQbA@mail.gmail.com> (raw)
In-Reply-To: <59df30e9-347f-d75d-66a1-c9357b9ef442@gmail.com>
> One of the main reasons I haven't put in the effort to update the cmake
> package is that recent versions of cmake have new dependencies which it
> vendors by default, which is not the way distros such as cygwin prefer to
> build things. For a cygwin packaging build of cmake (as with other tools),
> the "right way" is presumably to use system versions of all library
> dependencies.
Cmake 3.12.0 builds successfully out of box for Cygwin with default build
script provided by Kitware.
So I think its a good chance to build and update the package. Moreover I
tested it in lots of our C++
projects that must be build under Cygwin via Appveyor CI. For this reason I
add pre-build step with
building the latest cmake:
- if "%type%"=="Cygwin" appveyor-retry appveyor DownloadFile "
https://cmake.org/files/v3.12/cmake-3.12.0.tar.gz" -FileName "cmake.tar.gz"
- if "%type%"=="Cygwin" C:\cygwin64\bin\bash -lc "cd
$APPVEYOR_BUILD_FOLDER; mkdir temp; cd temp; mv ../cmake.tar.gz
./cmake.tar.gz; tar xzf cmake.tar.gz --strip-components=1; ./bootstrap &&
make && make install; cd ..; rm -rf ./temp"
Of course the best solution for us is to have cmake 3.12.0 updated in
Cygwin repository, because its building time is about ~30min
next prev parent reply other threads:[~2018-07-26 9:28 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 [this message]
2018-07-26 19:05 ` Tony Kelman
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=CAHVoUt2PVbACqMpJGjTjArkaJKbi95zQzNL4bo45QCyumbpQbA@mail.gmail.com \
--to=chronoxor@gmail.com \
--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).