Hmm, it seems like a lot of meson ports are adding a dependency on
x11/gnome by doing MODULES = devel/meson x11/gnome. I assume it is to
get around this limitation.
On 5/15/21 12:11 PM, Aisha Tammy wrote:
Hi all,
It seems like the meson.port.mk adds to CONFIGURE_ENV +=
CXXFLAGS="${CXXFLAGS}" and when I want to add CONFIGURE_ENV =
CXXFLAGS="${CXXFLAGS} -I${LOCALBASE}" it gets overriden by the
meson.port.mk to go back to -O2 -pipe and then the has_header
functions start failing during the configure phase.
After looking at the code in the meson.port.mk the best solution to
come to my mind is to define CXXFLAGS += -I${LOCALBASE}/include
outside of CONFIGURE_ENV and then it can be picked up by
MODMESON_CONFIGURE_ENV but this feels wrong.
Is there anyway to get around this?
Thanks,
Aisha
