public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: brendan detracey <brendandetracey@yahoo.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: eccodes
Date: Sun, 11 Apr 2021 16:48:54 +0000 (UTC)	[thread overview]
Message-ID: <1777022414.443732.1618159734064@mail.yahoo.com> (raw)
In-Reply-To: <1777022414.443732.1618159734064.ref@mail.yahoo.com>

Hi,
eccodes builds out of the box, more or less. However, all tests fail because the cyg*.dll's weren't copied to ${B}/bin. (They were handled properly when built without cygport i.e. copied from src and fortran subdirs of the build dir.)
What have I done wrong?
Apologies for cut and paste. I have yet to learn git. It is on the list... 

Finally, is there template for passing the number of processors minus 1 to cygport for all compiling and testing? If so, will cygport pass it automatically through cygcmake to its makefile generator and to cygtest? It would be nice to speed up my compile.
Thanks,Brendan

eccodes.cygport-----------------------------------------------------------------------------------inherit cmake
shopt -s extglob
# WARNING: source download link has to be hard-coded :(# The eccodes cmake default install location is usr/local
NAME="eccodes"VERSION=2.21.0RELEASE=1
CATEGORY="Science"SUMMARY="ECMWF tools to decode and encode WMO GRIB and BUFR file formats, and decode WMO GTS file format"DESCRIPTION="ecCodes is a package developed by ECMWF which provides an API and a set of tools\ for decoding and encoding messages in the following formats\:\ WMO FM-92 GRIB edition 1 and edition 2\ WMO FM-94 BUFR edition 3 and edition 4\  WMO GTS abbreviated header (only decoding)"
HOMEPAGE="https://confluence.ecmwf.int/display/ECC/ecCodes+Home"SRC_URI="https://confluence.ecmwf.int/download/attachments/45757960/eccodes-2.21.0-Source.tar.gz" SRC_DIR="${PN}-${PV}-Source"
PKG_NAMES="eccodes libeccodes libeccodes-devel"
eccodes_CONTENTS="  usr/local/bin/!(cyg*dll)  usr/local/share"
libeccodes_CATEGORY="Libs"libeccodes_SUMMARY="${SUMMARY} (runtime)"libeccodes_CONTENTS="  usr/local/bin/cyg*dll"
libeccodes_devel_CATEGORY="Libs"libeccodes_devel_SUMMARY="${SUMMARY} (development)"libeccodes_devel_CONTENTS="  usr/local/lib/  usr/local/include"
RESTRICT="diff"KEEP_LA_FILES="none"
# curl is required to download full test data set from ECMWF. Will this behave under CI?BUILD_REQUIRES="curl gfortran libnetcdf-devel libopenjpeg-devel libpng-devel libaec-devel libgomp1"
CYGCMAKE_GENERATOR="Unix Makefiles"CYGCMAKE_ARGS="    -DDISABLE_OS_CHECK=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DIEEE_LE=1    -DENABLE_NETCDF=ON -DENABLE_JPG_LIBOPENJPEG=ON -DENABLE_PNG=ON -DENABLE_AEC=ON -DENABLE_FORTRAN=ON -DENABLE_ECCODES_OMP_THREADS=ON -DENABLE_MEMFS=OFF -DENABLE_EXTRA_TESTS=ON"

       reply	other threads:[~2021-04-11 16:48 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 ` brendan detracey [this message]
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           ` eccodes Marco Atzeri
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=1777022414.443732.1618159734064@mail.yahoo.com \
    --to=brendandetracey@yahoo.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).