From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
	ip-172-31-65-14.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=3.0 tests=BAYES_40,FREEMAIL_FROM,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
X-Received: by 2002:ae9:e919:0:b0:6e0:90df:228f with SMTP id x25-20020ae9e919000000b006e090df228fmr2282787qkf.756.1669016706953;
        Sun, 20 Nov 2022 23:45:06 -0800 (PST)
X-Received: by 2002:a05:620a:4884:b0:6fb:c38e:27bf with SMTP id
 ea4-20020a05620a488400b006fbc38e27bfmr14950810qkb.351.1669016706752; Sun, 20
 Nov 2022 23:45:06 -0800 (PST)
Path: eternal-september.org!reader01.eternal-september.org!border-1.nntp.ord.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sun, 20 Nov 2022 23:45:06 -0800 (PST)
In-Reply-To: <lyzgclwc6t.fsf@pushface.org>
Injection-Info: google-groups.googlegroups.com; posting-host=2a01:e0a:810:89e0:58b4:5438:3a7b:8a83;
 posting-account=6yLzewoAAABoisbSsCJH1SPMc9UrfXBH
NNTP-Posting-Host: 2a01:e0a:810:89e0:58b4:5438:3a7b:8a83
References: <a478cf79-687b-4c03-94bf-01c982ff277bn@googlegroups.com>
 <ly8rk6y4qz.fsf@pushface.org> <3e7e9f66-9e74-4a04-98d9-73cc14d7e80bn@googlegroups.com>
 <lyzgclwc6t.fsf@pushface.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <13bd6b02-2214-45aa-bdbb-900b1753baf1n@googlegroups.com>
Subject: Re: How to build Python3 support into GNATCOLL with alire
From: Emmanuel Briot <briot.emmanuel@gmail.com>
Injection-Date: Mon, 21 Nov 2022 07:45:06 +0000
Content-Type: text/plain; charset="UTF-8"
Xref: reader01.eternal-september.org comp.lang.ada:64641
List-Id: <comp.lang.ada>

Hi Simon,

I have not used alire myself, but I noticed the following in your message:

> Alire 1.3 will support Homebrew as the package manager for macOS, but 
> someone has to work out how to upgrade the above two items to use it 
> (and how to approach include, library paths; the ideal way would 
> probably be to use pkg-config to determine them, but the simplest way of 
> doing that would mean running a script from within gprbuild - not going 
> to happen. 

Although running external scripts from gprbuild is indeed unlikely, it is definitely in the realms of gprconfig (which is run first to generate the .cgpr config file).
For this one would need to provide some .xml file that explains what command to run, and what to generate in the .cgpr file (likely adding some `-I` compiler
switches for C files).

Emmanuel