On Thu Feb 27, 2020 at 08:35:41AM +0100, Landry Breuil wrote:
> On Thu, Feb 27, 2020 at 07:59:32AM +0100, Rafael Sadowski wrote:
> > Hi All
> >
> > After truly hard work, I am excited to write this email. The
> > following diff contains the 3 ports which are all dependent on each
> > other.
> >
> > - devel/py-sip
> > - x11/py-qt5
> > - x11/qt5
> >
> > Almost all consumers fixed. For some you will find patches on
> > ports@, for some, private maintainer emails are out. math/octave is not
> > happy now but maybe an update helps. I'll take care of this monster.
> >
> > What's the news?
> >
> > - Most of the work was done in qtbase.
> > - The qtbase port comes with vulkan and zstd support by default enabled.
> > I hope this will works fine with !{amd64,i386} arches.
> > - s/c++11/c++17/
> > - Qtdoc (docs) is broken again, I think I am not that bad again and can
> > be fixed later.
> > - Bump all shred lib and cleanup SHARED_LIBS.
> > - Many cleaning jobs in the Makefiles.
> > - New py-qt5/pkg/PFRAG.python3. Could the py- wizards take a look at this.
>
> can you explain why ? the MODPY_COMMENT bit should achieve the same in
> the current port.. unless i missed something ?
I can't, this works for me. I'm not the py-{port} expert maybe there is
a smarter/cleaner way to do it.
>
> > - patch-qmake_generators_unix_unixmake_cpp
> > -- That was the biggest problem, at the p2k19 I decided to solve by:
> > "Transform /usr/ports/pobj/xxx/lib/libQt5Core.so into
> > -L/usr/ports/pobj/xxx/build-amd64/lib -lQt5Core" ... works!
>
> i suppose that lead to issues when linking qmake projects ? seems to be
> fine fixed this way, but im no linker expert.
It shouldn't be. This patch is for qmake code or respectively qmake
itself.
>
> > Looking forward for feedback.
>
> will build all this and my qt5 apps (ie mostly qgis & keepassxc) and
> dogfood all this on amd64, thanks for the hard work :)
keepassxc works fine here fine for over weeks.
