X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Pb9y5D2Miz4OYyIu
	SLlka3fwwWSyZ9i22NZPehV1hbT/3p9kGkwkhNWj689l1iakZcXKAKOlPiAfbuH/
	dmuRUvG1RfPANPqH0dZaNHmrU6PE6jIGckXZZ9QRlKVGgqeQto1KqBIPUapL6gUn
	+QSCWOrfq+WorYxQ03dMazWsVfI=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=HshWvU5IHrcE9YEf7uNg+D
	NXifU=; b=Y1Hqcevf6aKVj9QKlRoE8Az0J1Q2jGrZ0ymIakt5vK2hJEut7A3G4n
	5o6TTkedCQb27SznV6tf0k2VGcKNNvzyrW+dBqmWvfF41Wz8g/z5giUAh7GeZa2/
	OyzpsZoe2viIXEMUCkZiaJH+Pt8gpTcdzxxv9EDJC7gItAm6wU4dM=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.0 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=H*r:4.86_1, HX-OutGoing-Spam-Status:score, lmh, world's
X-HELO:	ecbiz204.inmotionhosting.com
Subject:	Re: problem building with cmake under cygwin (need clang)
To:	cygwin AT cygwin DOT com
References:	<5796B2A7 DOT 8060002 AT molconn DOT com> <CAEhDDbBsAGK69QyXLzjQu3JQSjD-vje6bhkzJPRo+poRzmrt4Q AT mail DOT gmail DOT com> <57977D6D DOT 7050203 AT molconn DOT com> <a1fc6589-8803-0661-1afa-d29d782b55aa AT gmail DOT com> <CAEhDDbCcH=Dk=6LEKXbn5Ez-pJD-nBuJuSj0nYKp40+zNVRjzA AT mail DOT gmail DOT com> <321cb4dd-4e13-b321-a21e-b7257c4787b5 AT gmail DOT com>
From:	LMH <lmh_users-groups AT molconn DOT com>
Message-ID:	<579BC47B.4090902@molconn.com>
Date:	Fri, 29 Jul 2016 17:02:51 -0400
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40
MIME-Version:	1.0
In-Reply-To:	<321cb4dd-4e13-b321-a21e-b7257c4787b5@gmail.com>
X-OutGoing-Spam-Status:	No, score=-1.0
X-Get-Message-Sender-Via:	ecbiz204.inmotionhosting.com: authenticated_id: lmh_users-groups AT molconn DOT com
X-IsSubscribed:	yes

Marco Atzeri wrote:
> On 27/07/2016 09:51, Csaba Raduly wrote:
>> On Tue, Jul 26, 2016 at 6:06 PM, Marco Atzeri  wrote:
>>>
>>> Csaba was clear but it seems you are misunderstanding,
>>> the call to cmake is
>>>
>>>        cmake [options] <path-to-source>
>>
>> No, not <path-to-source> but <path-to-CMakeLists.txt>
>>
>> For quickhull, CMakeLists.txt is in the root of the project, the
>> sources are under the src directory.
>
> Csaba,
> you are 100 %right.
> I just copied the cmake help
>
> $ cmake --help |head -n 4
> Usage
>
>    cmake [options] <path-to-source>
>    cmake [options] <path-to-existing-build>
>
> where of course they consider CMakeLists.txt as part of the source
> and placed in the tree root.
>
>> Regardless of where the build is performed, the path in the cmake
>> invocation must point to the root of the project. Copying
>> CMakeLists.txt into ./src and pointing cmake to ./src is unlikely to
>> work.
>>
>> All of this is moot because the author of quickhull littered
>> CMakeLists.txt with clang-specific compiler switches. He made no
>> attempt to cater for the world's most widely used C++ compiler (GCC).
>
> I agree on that. He made the life hard for anyone to build his software.
>
>>
>> Csaba
>
> Regards
> Marco
>
>
>
> --
> 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


I decided to try this on opensuse to see if that made a difference. After updating to 
cmake 3.6 and installing clang, the command with pdw as /build,

cmake -DCMAKE_CXX_COMPILER=clang ..

gives the following output without error,

-- The C compiler identification is GNU 4.8.3
-- The CXX compiler identification is Clang 3.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/clang
-- Check for working CXX compiler: /usr/bin/clang -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test COMPILER_SUPPORTS_LIBCXX
-- Performing Test COMPILER_SUPPORTS_LIBCXX - Success
-- Performing Test COMPILER_SUPPORTS_CXX1Z
-- Performing Test COMPILER_SUPPORTS_CXX1Z - Success
-- Wrong build type selected, default to Debug.
-- Configuring done
-- Generating done
-- Build files have been written to: /home/user1/ATomilov_quickhull/trunk/build

You can see that the above is different then the results with cygwin,

-- The CXX compiler identification is Clang 3.5.0
-- Check for working CXX compiler: /usr/bin/clang -- works

The above did not appear to build the application in that I don't see any binaries 
that were created. It looks like the command cmake -DCMAKE_CXX_COMPILER=clang .. just 
configured the build without actually compiling and building the application.

Do I need to do something different to get the application to be created? I have 
never used cmake before and am more than a bit out of my depth here.

At any rate, the above suggests that there is an issue with my cygwin installation 
here and possibly that clang isn't working. Does my output from cygcheck suggest 
anything?

LMH





--
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

- Raw text -