On Sat, Mar 23, 2019 at 15:07:39 +0100, Gregor Jasny via cmake-developers wrote:
> in the past when building CMake (itself) I spent long times waiting for
> configuration of the embedded libraries. Mostly libcurl send / receive
> signature detection. Today I had the idea of using system libraries
On Mon, Mar 11, 2019 at 16:50:21 +0100, workbe...@gmx.at wrote:
> i play around much with ExternalProject_Add and i found some kind of
> "error". When fetching big repositories like llvm cmake don't show any
> output when cloning the repository which makes the user believe cmake
> stucks, is there
On Tue, Jan 22, 2019 at 19:31:43 +0100, tors...@robitzki.de wrote:
> Currently, the Code that evaluates the ${}-Syntax only evaluates the key, if
> the key is not an empty string:
>
> const char* cmCommandArgumentParserHelper::ExpandSpecialVariable(
> const char* key, const char* var)
> {
> i
On Mon, Dec 31, 2018 at 15:30:28 -0800, Saleem Abdulrasool wrote:
> AFAIK, the driver interface is supposed to be stable. The frontend options
> are not, but, the same holds true for clang as well. The driver options
> are stable, and we (as the clang developer community) aim to not break
> that.
On Sun, Dec 30, 2018 at 13:09:23 -0800, Saleem Abdulrasool wrote:
> I was looking at supporting Swift as a language in CMake. I know that
> CMake has some preliminary support that assumes that you are building on
> macOS with Xcode. I am trying to support building swift libraries and
> executable
