1. When Qt4 came in, there were almost no qmake4 users.
Now there are many:
cad/fritzing/Makefile: ${LOCALBASE}/bin/qmake4 -o Makefile phoenix.pro
cad/openscad/Makefile: ${SETENV} ${QMAKE_ENV} qmake4 ${QMAKE_FLAGS}
openscad.pro
devel/beediff/Makefile: cd ${WRKSRC} && ${LOCALBASE}
20 дек. 2014 г. 1:37 пользователь "Vadim Zhukov"
написал:
>
> 1. When Qt4 came in, there were almost no qmake4 users.
>Now there are many:
>
> cad/fritzing/Makefile: ${LOCALBASE}/bin/qmake4 -o Makefile
phoenix.pro
> cad/openscad/Makefile: ${SETENV} ${QMAKE_ENV} qmake4 ${QMAKE_FLA
2014-12-20 1:37 GMT+03:00 Vadim Zhukov :
> 1. When Qt4 came in, there were almost no qmake4 users.
>Now there are many:
>
> cad/fritzing/Makefile: ${LOCALBASE}/bin/qmake4 -o Makefile
> phoenix.pro
> cad/openscad/Makefile: ${SETENV} ${QMAKE_ENV} qmake4 ${QMAKE_FLAGS}
> openscad.p
On 2014-12-19, Vadim Zhukov wrote:
> 2. Now that Qt5 is coming in, and given that some ports already (and
>many more will) support both Qt4 and Qt5, it may result in
>maintaince burden, to tweak each such port in the way:
>
> .if ${FLAVOR:Mqt5}
> ...
> .else
> ...
> .endif
Why even do th
20 дек. 2014 г. 19:59 пользователь "Christian Weisgerber" <
na...@mips.inka.de> написал:
>
> On 2014-12-19, Vadim Zhukov wrote:
>
> > 2. Now that Qt5 is coming in, and given that some ports already (and
> >many more will) support both Qt4 and Qt5, it may result in
> >maintaince burden, to
