Sounds good.
13 июл. 2017 г. 11:13 ПП пользователь "Rafael Sadowski" <
raf...@sizeofvoid.org> написал:
>
>
> On Thu Jul 13, 2017 at 06:31:17PM +0300, Vadim Zhukov wrote:
> > 2017-07-12 21:35 GMT+03:00 Rafael Sadowski <raf...@sizeofvoid.org>:
> > > Hi All.
> > >
> > > please find attached a new port security/qca-qt5 (QCA for Qt5). This is
> > > separate port for Qt5 because it's too different from Qt4 case. Initial
> > > work from zhuk@ on openbsd-wip in 2016. This port is not very
> different
> > > from current security/qca port in CVS and includes all tweaks of the
> > > last days/hours. It has no plugin FAVORS because there are no
> consumers.
> > >
> > > Tested with upcoming net/konversation update on amd64.
> > >
> > > OK to import?
> >
> > The port puts crypto.prf into the /usr/local/mkspecs/, which is wrong.
> > Please add the following to CONFIGURE_ARGS:
> >
> > -DQCA_FEATURE_INSTALL_DIR=${MODQT_LIBDIR}/mkspecs/features
> >
> > rebuild and regen PLIST then.a
>
> Ok with?:
>
> https://github.com/jasperla/openbsd-wip/commit/
> 70e08a7b7cd55d431d69ecc878de1edbe5f76c87
>
>
> >
> > Also, When building with clang it picks up libc++ and libc++abi, but
> > I'm not sure if this is because I have Qt5 built with egcc right now,
> > so don't worry about that. Probably worths a "TODO: recheck WANTLIB on
> > clang arch", though.
>
> In my opinion this is not necessary. We must to check all qt+clang ports.
>
> >
> > I'm still a bit worried about outdated parts of Botan (documentation
> > said it was Botan 1.6) so called "botantools" inside QCA, but that's a
> > totally different issue...
>
> Agree, but we don't build qca-botan or any other plugin in qca-qt5.
>
> Rafael
>
