public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Pavel Fedin" <p.fedin@samsung.com>
To: <Brian.Inglis@SystematicSw.ab.ca>, <cygwin@cygwin.com>
Subject: RE: cmake and Code::Blocks
Date: Fri, 14 Jun 2019 11:13:00 -0000	[thread overview]
Message-ID: <000501d522a2$3dc90c10$b95b2430$@samsung.com> (raw)
In-Reply-To: <3fa745b4-b8d7-d050-b26b-8c1df388629b@SystematicSw.ab.ca>

 Hello!

> What evidence do you have of features that support Cygwin?

 In the project configuration i can choose "Cygwin toolchain", and it correctly detects c:/Cygwin as installation root.

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

 Well, this is too philosophical IMHO and is outside of question's scope.
 My takeout from your reply so far:
 1. No, there is no special support in CMake and there will never be one because mixing native Windows tools and Cygwin tools is not supported by Cygwin project
 2. You don't know whether Code::Blocks has any special support for Cygwin paths.

 Thank you very much for your time, i'll try to raise this in CMake development community and/or Code::Blocks development community. This issue could be solved on both sides.

Kind regards,
Pavel Fedin
Senior Engineer
Samsung Electronics Research center Russia


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

      reply	other threads:[~2019-06-14 11:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20190613101352eucas1p2e1d967dfe7e76437adb6a45ea10b1158@eucas1p2.samsung.com>
2019-06-13 10:13 ` Pavel Fedin
2019-06-13 11:34   ` Csaba Raduly
2019-06-13 12:29     ` Pavel Fedin
2019-06-13 18:20   ` Brian Inglis
2019-06-14 11:13     ` Pavel Fedin [this message]

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='000501d522a2$3dc90c10$b95b2430$@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=Brian.Inglis@SystematicSw.ab.ca \
    --cc=cygwin@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).