X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org BD48D3857407
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1634473593;
	bh=kDFyTNqBbwQFzKmbM8kH8ZeAFFO3h0gG/p3dp3ZO0O0=;
	h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=HLa3ddKzO2p3cAZNK0evZbGOT9YlrIglbmzAvA0dWJ/oP6JYuQJvupOAVlYMdl6xd
	BiS9qHXoDvBPFEhGNG+DEDWzcPwO47n0pdNlaqOE8O22njmJ8DfvNcgEhUFYCIP6dD
	z3bRspZNRwRR14memglj+lczTCGmU31IM8jMC0tI=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org B2A263858D35
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20210112;
	h=x-gm-message-state:mime-version:references:in-reply-to:from:date
	:message-id:subject:to;
	bh=SABeuj/GgUyTa17kf1SgR7BokvbFjsttigMeW/N1ywU=;
	b=Ogo8ulRxiL3hPigOmEE5lpMrKxo5y2KnafPsezeIrsap+yCPyJR+M1ZuB9SApYmSvd
	pmJqGJ1I4lw4SIs0mmtBCry3jD+MaZI0SyXHC7fbcxuV0Gu4zbQgsQrbtdRFdjtXwiam
	bTa0emmEnUN1M183HyqJJYqrxls9fUP0TAGg58NU/i4XDhSa9gCkoby00YOiPRjvHlAp
	l4KBDR0Jn6z2SYZv7Ov3Ao4ytRBohjphDDMX0F4OsLBBR0Nt+SUGGb4uDDgxS+acucpj
	aVkn7KNGbhw1+6bxaSvIPQMk8MPpbybDIozjlkbbU/Gfl/J2zCcTcNLvH1EJfM7wGT7W
	aACA==
X-Gm-Message-State:	AOAM530UnGKiT+Grg27BzC8IsawPescRSpq4faIZzdTxqYjny7B7HZbZ
	T2pvzuzqFWAPB/PzB8O7W/sptK+oLnAy50o4LO6XrHZ1PzE=
X-Google-Smtp-Source:	ABdhPJw1diAJJoa6cklGYl2eveFq8q1pUiZjLjinGZkVaPoJrerM02xQL+sCu2t535AoDgJaGY6t8fp8nsCGBTl4io0=
X-Received:	by 2002:a17:906:919:: with SMTP id
	i25mr21841857ejd.171.1634473560744;
	Sun, 17 Oct 2021 05:26:00 -0700 (PDT)
MIME-Version:	1.0
References:	<CADt9576V=QzeWX+617wFt4CNYQLmJQiF2Ov3QdFHa=bcHh7P5A AT mail DOT gmail DOT com>
	<ea4e2c7b-c810-c3e0-c53c-b7d61153cd66 AT SystematicSw DOT ab DOT ca>
In-Reply-To:	<ea4e2c7b-c810-c3e0-c53c-b7d61153cd66@SystematicSw.ab.ca>
Date:	Sun, 17 Oct 2021 14:25:53 +0200
Message-ID:	<CADt9577CGk1ovmnWHYba6BfkitupTvrZAbz4ru7HE4n-oq5Z5g@mail.gmail.com>
Subject:	Re: CYGPORT: using WAF build system.
To:	cygwin AT cygwin DOT com
X-Spam-Status:	No, score=-1.2 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,
	SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	"Carlo B. via Cygwin" <cygwin AT cygwin DOT com>
Reply-To:	"Carlo B." <carlo DOT bramini AT gmail DOT com>
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Hello,
thank you very much for the replies.
I have successfully compiled lv2, lilv, serd, sord, sratom (but not
suil yet) for CYGWIN and I made the packages for building the master
branch of Audacity.
I also tried to do the same thing for i686 and x86_64, by using
provided MinGW-w64 cross compiler, but I'm getting this message:

*** ERROR: waf.cygclass does not yet support cross-compiling

I hope that somebody may fix this in the future.
Sincerely.

Il giorno ven 15 ott 2021 alle ore 17:22 Brian Inglis
<Brian DOT Inglis AT systematicsw DOT ab DOT ca> ha scritto:
>
> On 2021-10-14 04:02, Carlo B. via Cygwin wrote:
> > I would like to make a package with LV2 plugins for CYGWIN.
> > The problem is that those plugins are using the WAF build system and
> > it is not clear to me how to proceed. Do you know if some of the
> > existing packages for CYGWIN are using WAF, so that they could be uses
> > as example for starting?
>
> In connection with other queries, I just came across a few lv2 packages
> already available in Cygwin:
>
> lv2
> lv2core
> lv2-calf
> lv2-devel
> lv2-examples
> lv2-swh
>
> slv2
> libslv2_9
> libslv2-devel
>
> with cygport build control script definitions and patches available
> which use WAF:
>
> https://cygwin.com/git-cygwin-packages?p=git/cygwin-packages/lv2.git
> https://cygwin.com/git-cygwin-packages?p=git/cygwin-packages/lv2-swh.git
> https://cygwin.com/git-cygwin-packages?p=git/cygwin-packages/slv2.git
>
> so you could install cygport and any *lv2* package dependencies, clone
> these repos or download and untar the current source packages which
> contain these files plus upstream tars, and build the current packages
> as a proof of concept and way of learning cygport, before trying to
> build more current versions.
>
> The simple approach to running cygport is to change to the directory
> containing the .cygport definitions and .patch file(s) or move them to a
> working directory (normally named for the source package), then run e.g.
>
>         $ cygport lv2.cygport get prep
>
> which downloads the upstream (not Cygwin) package sources for the
> specified version to a central cache directory, creates a package build
> directory, copies or untars sources if required, and (tries to) apply
> any patches to the original sources, to give you working sources, which
> you can then use to compile and make install-able Cygwin packages for
> the current arch.
> You can try one of the following examples, depending whether you want to
> watch the builds run or review the results later:
>
>         $ cygport lv2.cygport all |& tee lv2-cygport-`arch`-all.log
>
>         $ cygport lv2.cygport all | tee lv2-cygport-`arch`-all.log 2>&1
>
>         $ cygport lv2.cygport all &> tee lv2-cygport-`arch`-all.log &
>
>        $ cygport lv2.cygport all > tee lv2-cygport-`arch`-all.log 2>&1 &
>
> Browse the created build subdirectories to see what is produced and
> review all detail logs generated during the process.
>
> After a successful build and package creation, it is always a good idea
> to try to run any test suites with:
>
>    $ cygport lv2.cygport check > tee lv2-cygport-`arch`-check.log 2>&1 &
>
> I use the cygport command check instead of test as test is used
> ambiguously by cygport, as it may also refer to test vs stable or
> production releases produced by cygport using commands e.g. all-test.
>
> --
> 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.
> [Data in binary units and prefixes, physical quantities in SI.]

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -