Re: [libgpiod][PATCH 3/3] Android.bp: initial addition

[Bartosz Golaszewski <brgl@xxxxxxxx>]

On Mon, Aug 17, 2020 at 6:24 PM Bartosz Golaszewski <brgl@xxxxxxxx> wrote:
>

[snip]

> > >
> > > I don't know Android very well but if its build system can launch
> > > autotools, then maybe you could autotoolify this file by providing
> > > Android.bp.in and letting autotools expand this macro?
> >
> > No unfortunately that is not how the AOSP build system works (or at
> > least I'm not aware of it).
> > AFAIK all the open-source projects used in AOSP (see external/ folder)
> > have a separate Android.bp alongside the autotools files.
> >
> > Here are a few examples of Android.bp files added by Google to
> > well-known projects:
> > - curl [1]
> > - iputils [2]
> > - strace [3]
> >
> > In the case above it is up to Google to maintain that file as only
> > hosted on their servers (not merged upstream).
> > But some other projects are ok merging it which makes it easier (at
> > least for me) like can-utils [4].
> >
>
> I'm perfectly fine with merging this file but I don't like having
> another place to look at when bumping the version number. I bunched up
> all API and ABI versions together in configure.ac in order to not
> forget anything when making new releases.
>
> I'm sure Android's build system is not as limited as not to allow to
> run some external scripts that would at least fetch the current
> version from configure.ac, is it?
>

Can you do something like this[1] but make the command fetch the
version string from configure.ac?

Bartosz

[1] http://androidxref.com/9.0.0_r3/xref/external/libmojo/Android.bp#67

[snip]