From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: eccodes
Date: Mon, 12 Apr 2021 09:07:37 +0200 [thread overview]
Message-ID: <96280ec3-e923-3da1-6578-c96368699e87@gmail.com> (raw)
In-Reply-To: <719120829.476733.1618178001957@mail.yahoo.com>
Brendan,
Bottom post on Cygwin mailing lists, please
On 11.04.2021 23:53, brendan detracey via Cygwin-apps wrote:
> That worked Marco. Thanks guys!How did "cygmake test" know it had to call "ctest"? In the eccodes instructions, "ctest" is the command.
It is on the makefile
-------------------------------------------------------------------
# Special rule for the target test
test:
@$(CMAKE_COMMAND) -E cmake_echo_color --switch=$(COLOR) --cyan
"Running tests..."
/usr/bin/ctest.exe --force-new-ctest-process $(ARGS)
.PHONY : test
-------------------------------------------------------------------
> Why doesn't cygport automatically symlink the cyg*dll files for tests?
It should be upstream instruction for testing where to find the
shared lib or they are expecting to test after installation.
It is not a problem with automake/autoconf as it is managed properly.
This workaround is relative common in these cases
> On Sunday, April 11, 2021, 04:43:41 p.m. ADT, Marco Atzeri via Cygwin-apps wrote:
>
> Brendan,
> no idea why on your build the installation is under /usr/local
> for me everything is in the right place.
> Please verify if you have some settings interfering
>
> Attached version that allows tests to be passed
>
> Regards
> Marco
>
>
>
next prev parent reply other threads:[~2021-04-12 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1777022414.443732.1618159734064.ref@mail.yahoo.com>
2021-04-11 16:48 ` eccodes brendan detracey
2021-04-11 18:01 ` eccodes Achim Gratz
2021-04-11 18:53 ` eccodes Brian Inglis
2021-04-11 19:43 ` eccodes Marco Atzeri
2021-04-11 21:53 ` eccodes brendan detracey
2021-04-12 7:07 ` Marco Atzeri [this message]
2021-04-12 19:22 ` eccodes Achim Gratz
2021-04-12 22:46 ` eccodes Brian Inglis
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=96280ec3-e923-3da1-6578-c96368699e87@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@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).