Alonso Schaich writes:
> SVN commit 10439 by aschai:
>
> Revert r10358.
FYI, explaining "why" would have been very good here, otherwise 2 years
from now one will have no idea of what caused this to be reverted.
___
kde-freebsd mailing list
kde-freebsd@
SVN commit 10439 by aschai:
Revert r10358.
M +2 -0 Makefile
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
On Wed, 22 Oct 2014 21:44:43 +0300
Raphael Kubo da Costa wrote:
> Max Brazhnikov writes:
>
> > On Sun, 05 Oct 2014 12:20:38 -0700 Alonso Schaich wrote:
> >> SVN commit 10358 by aschai:
> >>
> >> Remove USES.
> >>
> >> devel/py-qt4 redundandly adds python USES as it's also added in the
> >> inc
SVN commit 10438 by rakuco:
Merge devel/qt5-qmldevtools into lang/qt5-qml.
qt5-qmldev only worked as a standalone port with a lot of duct tape and our
hacks that invoked qmake from a subdirectory of ${WRKSRC}.
Since the latter does not work anymore, we cannot build qt5-qmldevtools as
we did befo
SVN commit 10437 by rakuco:
bsd.qt.mk: Set QMAKESPEC instead of QMAKEPATH.
This partially reverts r8728.
QMAKEPATH does much more than we want now that we call qmake from the top of
${WRKSRC}. qmake uses QMAKEPATH when evaluating the QMAKE_MKSPECS property,
which is in turn used by qt_config.pri
SVN commit 10436 by rakuco:
Call qmake from the root of the ${WRKSRC}.
In Qt 5.3, Qt's build infrastructure has undergone some changes that make
our previous approach of calling qmake from the directories we want to build
stop working. Things would break even more in Qt 5.4, in which qtbase's
con
SVN commit 10435 by rakuco:
Stop explicitly passing ${LOCALBASE} to the compiler.
qmake's behavior has changed in Qt 5, and the paths set in QMAKE_INCDIR and
QMAKE_LIBDIR in the mkspecs are passed before any others, such as the ones
in the build directory themselves.
In practice, this means that
Max Brazhnikov writes:
> On Sun, 05 Oct 2014 12:20:38 -0700 Alonso Schaich wrote:
>> SVN commit 10358 by aschai:
>>
>> Remove USES.
>>
>> devel/py-qt4 redundandly adds python USES as it's also added in the included
>> bsd.pyqt.mk, so it should be safe to remove it from the devel/py-qt4
>> metapo
Max Brazhnikov writes:
>> Lastly, I'm fairly convinced 7492a2c ("Stop explicitly passing
>> ${LOCALBASE} to the compiler") is the only way to fix ports/194088, but
>> feedback is also welcome.
>
> This may break 3rd-party software and ports which relay on this includes,
> but I don't consider thi
On Sun, 19 Oct 2014 21:01:05 +0300 Raphael Kubo da Costa wrote:
> Hi everyone (particularly Max and Alberto),
>
> I believe all the work for updating Qt5 to 5.3.2 is done. I've been
> committing smaller parts of the required changes for a while now, but
> left the big, disruptive changes for the e
SVN commit 10434 by rakuco:
qmake5: Finish fixing the plist for 5.3.2.
M +41 -2 pkg-plist
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest informati
SVN commit 10433 by rakuco:
qmake5: Start using the new unsupported/freebsd-clang mkspec.
With the help of Gabriel de Dietrich from Digia, a new freebsd-clang mkspec
was added to Qt in the 5.3 release cycle.
Let us start using it: instead of creating mkspecs/freebsd-clang by copying
the freebsd-
On Tue, 21 Oct 2014 23:34:09 +0200
"lore...@piangatello.it" wrote:
> I've forgot to read UPDATING and no longer have the list of files
> contained in the old package...
>
> Any hint?
>
If you are refering to the contents installed by an old version of a
port/package, it is maintained by pkg an
I've forgot to read UPDATING and no longer have the list of files
contained in the old package...
Any hint?
Lorenzo
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for
14 matches
Mail list logo
