DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=nxiQ9DdPs94V8Gm7
	euK29OvjwXRx4+kZ/P6wkk/v1e1LvO+V666rSieG+qQ1hRtjOft1YCt4qfpFcCYj
	L4NRfFYJONOGx3DzLHIpq2J976niAEnJAgyHrl8Bfy8lfUBAsU6VmBShEGJKJZMF
	1UwoEcaNDK7NTmfLiJ1KGWZo2FY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Reply-To: Brian.Inglis@SystematicSw.ab.ca
Subject: Re: cmake and Code::Blocks
To: cygwin@cygwin.com
References: <CGME20190613101352eucas1p2e1d967dfe7e76437adb6a45ea10b1158@eucas1p2.samsung.com> <000701d521d0$b30374c0$190a5e40$@samsung.com>
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Openpgp: preference=signencrypt
Message-ID: <3fa745b4-b8d7-d050-b26b-8c1df388629b@SystematicSw.ab.ca>
Date: Thu, 13 Jun 2019 12:20:20 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <000701d521d0$b30374c0$190a5e40$@samsung.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 2019-06-13 04:13, Pavel Fedin wrote:
> I am working on a CMake-based project and building it under Cygwin. I
> decided to use Code::Blocks IDE since CMake already hass appropriate project 
> generator (i'm using "CodeBlocks - Unix Makefiles"). However, i had to
> manually edit the resulting .cbp file and replace all paths with their native
> Windows equivalents; otherwise the IDE can't find any file and do anything.
> Is this a known TODO area for CMake or am i missing some magic switch while 
> loading the project into CB?
If you are trying to use a Windows based tool with Cygwin utilities, you are
likely to be the first, and on your own.

What evidence do you have of features that support Cygwin? Maybe CB doesn't
support Cygwin tools, or not very well, or maybe you have to change the
configuration, or provide the conversion, or maybe it's just not a good IDE for
those tools?

Having to edit file paths used by a tool is never a good sign. There are
probably a lot of other paths you may have to edit. Sometime the trick is to add
a couple of your own scripts to convert the paths in files to and from Cygwin
and Windows: hint - cygpath.

How would anyone here know if you are missing some magic switch using the tool
you chose?

Read and understand the docs to know the limitations and interface requirements
of the tools you have chosen.
Sometimes we make bad choices, have to scrap what we did, make hopefully better
choices, and restart from earlier.
Source control allows you to handle that more easily.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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