public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cmake and Code::Blocks
Date: Thu, 13 Jun 2019 18:20:00 -0000	[thread overview]
Message-ID: <3fa745b4-b8d7-d050-b26b-8c1df388629b@SystematicSw.ab.ca> (raw)
In-Reply-To: <000701d521d0$b30374c0$190a5e40$@samsung.com>

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

  parent reply	other threads:[~2019-06-13 18:20 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 [this message]
2019-06-14 11:13     ` Pavel Fedin

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=3fa745b4-b8d7-d050-b26b-8c1df388629b@SystematicSw.ab.ca \
    --to=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).