Re: [new] audio/spotify-player / cargo.port.mk

Theo Buehler <tb@theobuehler.org> writes:

> I think sthen is right that a variable for this in cargo.port.mk would
> make sense to obviate the need to keep these in sync. On rust updates,
> all rust ports are rebulit anyway, so if rust switches to llvm 19 that
> would be picked up automatically.

I didn't precisly followed the problem that a variable in cargo.port.mk
should solve.

is it just to have clang-sys crate to have MAKE_ENV +=
LIBCLANG_PATH=/usr/local/llvm18/lib + BUILD_DEPENDS ?

and what is important ? llvm from ports (base vs ports version, whatever
the llvm version is) ? exact llvm version used in rustc ?

alsocurrently, nothing forbid that llvm version on one arch to be
different from another one (llvm from ports version X vs embedded llvm
version Y).

Thanks.
--
Sebastien Marie