On 2024/03/23 09:29, Rafael Sadowski wrote:
> On Sat Feb 17, 2024 at 09:08:19AM +, Stuart Henderson wrote:
> > You'll need to actually add it to BUILD_DEPENDS e.g.
> >
> > .if ${MODQT6_DEPS:L} == "yes"
> > BUILD_DEPENDS += ${MODQT6_BUILD_DEPENDS}
> > LIB_DEPENDS += ${MODQT6_LIB_DEPENDS}
> > .e
On Sat Feb 17, 2024 at 09:08:19AM +, Stuart Henderson wrote:
> You'll need to actually add it to BUILD_DEPENDS e.g.
>
> .if ${MODQT6_DEPS:L} == "yes"
> BUILD_DEPENDS += ${MODQT6_BUILD_DEPENDS}
> LIB_DEPENDS += ${MODQT6_LIB_DEPENDS}
> .endif
That's what I did, isn't it?
>
> But then you'll a
You'll need to actually add it to BUILD_DEPENDS e.g.
.if ${MODQT6_DEPS:L} == "yes"
BUILD_DEPENDS += ${MODQT6_BUILD_DEPENDS}
LIB_DEPENDS += ${MODQT6_LIB_DEPENDS}
.endif
But then you'll also need to knock out the dep in qttools itself and
anything that qttools depends on.
--
Sent from a phone,
OK to add qttools as a build dependency for all qt6 ports? We're doing
the same in qt5.port.mk.
I'm currently porting more and more Qt6 consumers that shows me that I
almost always need a tool from qttools.
Index: qt6.port.mk
===
RC