From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: How do I write a cygport file for two different configurations in the same cygport package
Date: Mon, 6 Apr 2020 05:12:35 +0200 [thread overview]
Message-ID: <3a1cee6f-d8f8-f0c9-ee89-1cfbccad4d14@gmail.com> (raw)
In-Reply-To: <a5d76b91-d0b0-6334-9701-ac33db6eaa2c@gmail.com>
Am 05.04.2020 um 22:51 schrieb Åke Rehnman via Cygwin:
> Hello all,
>
> I was going to update the libftdi1 package which in addition to the
> regular ftdi library contains python bindings. Unfortunately the cmake
> CMakeLists only builds python 3 bindings for this library unless
> explicitly passed some magic variables on the command line. However both
> python 2 and python 3 bindings cannot be built in one go.
>
> So the question is how do I write a cygport file to first compile the
> libraries with python 3 then reconfigure (run cmake again with new
> parameters) and build the python 2 bindings?
>
> Any ideas?
>
> BR
>
> /Ake
>
this is the solution implemented to build fftw3
3 times with different parameters.
I will use something similar for postgresql that has the same
problem of your libftdi1.
src_compile() {
cd ${S}
cygautoreconf
mkdir -p ${B}/float
cd ${B}/float
CYGCONF_SOURCE=${S} cygconf \
--enable-float \
--enable-threads \
--enable-shared --disable-static \
--enable-openmp \
--enable-sse -enable-avx \
--with-windows-f77-mangling
cygmake
mkdir -p ${B}/long
cd ${B}/long
CYGCONF_SOURCE=${S} cygconf \
--enable-threads \
--enable-shared --disable-static \
--enable-openmp \
--enable-sse2 -enable-avx \
--with-windows-f77-mangling
cygmake
mkdir -p ${B}/double
cd ${B}/double
CYGCONF_SOURCE=${S} cygconf \
--enable-long-double \
--enable-threads \
--enable-shared --disable-static \
--enable-openmp \
--with-windows-f77-mangling
cygmake
}
src_test() {
for precision in float long double
do
cd ${B}/${precision}/tests
cygtest
done
}
src_install() {
for precision in float long double
do
cd ${B}/${precision}
cyginstall
done
..
Regards
Marco
prev parent reply other threads:[~2020-04-06 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 20:51 Åke Rehnman
2020-04-06 3:12 ` Marco Atzeri [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=3a1cee6f-d8f8-f0c9-ee89-1cfbccad4d14@gmail.com \
--to=marco.atzeri@gmail.com \
--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).