Re: help with porting libaec

On Thu, 3 Jul 2025 12:23:29 +0200 Marco van Hulten wrote:
> Hello,
>
> I'm trying to port something. WIP is attached.
>
> When I grab the tar ball without 'configure', I have to generate it.
> This fails as follows:
>
> [...]
>
> Apparently it extracts under the directory with that long name and not
> $(DISTNAME). What went wrong?

I did not distinct between DISTNAME and PKGNAME. Fixed this now, sorry
for reporting such a trivial issue.


> There are also a libaec tarballs available with a generated configure
> script, but the one from the main mirror has a URL that changes
> unpredictable with new versions, as shown here:
> https://gitlab.dkrz.de/k202009/libaec/-/issues/6#note_344239

There is also a silly string in the extraction directory name:

DISTNAME = libaec-v$(VERSION)-7204505af7d6635734fc12a38d6bd0a6253c9c6d
PKGNAME = libaec-$(VERSION)

I suppose it is fine like this. I'll send a cleaned up port soon.
Comments (on tgz in original message) of course welcome.

Some open unurgent questions, useful to know nonetheless:

> When I use a tarball with generated files, libaec builds successfully.
>
> Are there reasons (except for success in this case) for using a tarball
> either with or without a configure script?
>
> CMake is apparently the preferred method for libaec, but is there any
> advantage there?

Thanks,

Marco