[SVN Commit] branches/plasma5/QT/www/qt5-webengine/files
SVN commit 12955 by tcberner: Import patches from www/chromium AMpatch-src_3rdparty_chromium_content_gpu_gpu__main.cc AMpatch-src_3rdparty_chromium_gpu_config_gpu__info__collector.cc
[SVN Commit] branches/plasma5/QT/www/qt5-webengine/files
SVN commit 12954 by tcberner: Import patch from www/chromium AMpatch-src_3rdparty_chromium_ui_gl_gl.gyp
[SVN Commit] branches/plasma5/QT/devel
SVN commit 12951 by tcberner: Try to make devel/qbs and devel/qtcrator upgradable, without the need to deinstall them first M +11 -0 qbs/Makefile M +12 -0 qtcreator/Makefile
[SVN Commit] branches/plasma5/QT/devel
SVN commit 12950 by tcberner: Update devel/qbs and devel/qtcreator to their newest releases M +2 -2 qbs/Makefile M +3 -3 qbs/distinfo D qbs/files (directory) M +14 -6 qbs/pkg-plist M +2 -3 qtcreator/Makefile M +3 -3 qtcreator/distinfo M +75 -86qtcreator/pkg-plist
[SVN Commit] branches/plasma5/CALLIGRA/editors/calligra-kf5-git
SVN commit 12949 by tcberner: Make stage-qa happy M +12 -7 Makefile
[SVN Commit] branches/plasma5/CALLIGRA/editors/calligra-kf5-git
SVN commit 12948 by tcberner: Hastily fix up calligra-kf5-git. This was forgotten when applications was updated to 16.08 where kdepimlibs5 is no longer a thing. However, as PIM in general is broken at the moment, as it deep down needs webengine, move it to an option for now M +7 -3 Makefile M +3 -3 distinfo M +4467 -4875 pkg-plist
FreeBSD 11.0 failures: kdenlive and k9copy-kde4
I just tried to build all ports on 11.0 that I have installed on 10.3. There were two unexpected failure: kdenlive and k9copy-kde4. kdenlive has two ambiguous uses of abs, k9copy-kde4 has one. For kdenlive, area51 seems to have the fix: http://src.mouf.net/area51/checkout/branches/plasma5/KDE/multimedia/kdenlive/files/patch-src_scopes_audioscopes_spectrogram.cpp I think the patch works. For k9copy-kde4, simply converting a difference of two uint32 values to int will not fix the abs at least on 32bit. Casting both to long long before should work. (Maybe it should rather be replaced by an "if".) With the patches attached, both ports build for me on 11.0-RC2/amd64. Cheers, Jan Henrik --- multimedia/k9copy-kde4/files/patch-src__backup__k9dvdbackup.cpp.orig 1970-01-01 00:00:00.0 + +++ multimedia/k9copy-kde4/files/patch-src__backup__k9dvdbackup.cpp 2016-09-03 12:13:02.510163000 + @@ -0,0 +1,11 @@ +--- src/backup/k9dvdbackup.cpp.orig 2009-12-06 10:13:36.0 + src/backup/k9dvdbackup.cpp 2016-09-03 12:12:26.764957000 + +@@ -885,7 +885,7 @@ + + + if ((vobu1 !=NULL) && (vobu2!=NULL)) { +-*_offset = abs(vobu1->newSector - vobu2->newSector) | maskOffset1 ; ++*_offset = abs((long)vobu1->newSector - (long)vobu2->newSector) | maskOffset1 ; + *_offset |= maskOffset2; + return vobu2; + } --- multimedia/kdenlive/files/patch-src__scopes__audioscopes__spectrogram.cpp.orig 1970-01-01 00:00:00.0 + +++ multimedia/kdenlive/files/patch-src__scopes__audioscopes__spectrogram.cpp 2016-09-03 11:40:42.543309000 + @@ -0,0 +1,20 @@ +--- src/scopes/audioscopes/spectrogram.cpp.orig 2014-08-14 23:57:34.0 + src/scopes/audioscopes/spectrogram.cpp 2016-09-03 11:40:07.737834000 + +@@ -241,7 +241,7 @@ + x = leftDist + (m_innerScopeRect.width()-1) * ((float)hz)/m_freqMax; + + // Hide text if it would overlap with the text drawn at the mouse position +-hideText = m_aTrackMouse->isChecked() && m_mouseWithinWidget && abs(x-(leftDist + mouseX + 20)) < (int) minDistX + 16 ++hideText = m_aTrackMouse->isChecked() && m_mouseWithinWidget && abs((int)(x-(leftDist + mouseX + 20))) < (int) minDistX + 16 + && mouseX < m_innerScopeRect.width() && mouseX >= 0; + + if (x <= rightBorder) { +@@ -269,7 +269,7 @@ + } + // Draw the line at the very right (maximum frequency) + x = leftDist + m_innerScopeRect.width()-1; +-hideText = m_aTrackMouse->isChecked() && m_mouseWithinWidget && abs(x-(leftDist + mouseX + 30)) < (int) minDistX ++hideText = m_aTrackMouse->isChecked() && m_mouseWithinWidget && abs((int)(x-(leftDist + mouseX + 30))) < (int) minDistX + && mouseX < m_innerScopeRect.width() && mouseX >= 0; + davinci.drawLine(x, topDist, x, topDist + m_innerScopeRect.height()+6); + if (!hideText) {
Re: First try at a digikam-kf5 port
So I've updated the port skeleton. I think it now covers all of the kf5 and qt5 USES properly. I've also brought in the DOCS and NLS options. I've also added the multimedia option that will do thumbnailing and playback via qt5-multimedia. This has been tested locally with the qt5.6.1-multimedia and is pretty dang slick. The digikam DEPENDENCIES file lists this option as needing more testing as some earlier versions of qt5-multimedia had bugs with gstreamer 1.0. I've yanked the gphoto2 pending some patching and testing, but hopefully camera integration will return sooner rather than later. This version I feel confident enough about that I'd say it's worth a commit pending approval of the freebsd-kde maintainers. Thomas Legg On Thu, Sep 1, 2016 at 4:41 PM, Tobias C. Bernerwrote: > Hi there > > I'd rather have -docs and -l10n as options than separate ports [as it is > the same distfile] -- if at all (I don't really see a good reason not to > install either docs or translations -- we should ship the complete thing by > default). > > And then, the Makefile.common rather belongs to the kipiplugin metaport > than to digikam itself. > > Yes, I think appending a -kf5 to the ports would be the right nameing > scheme here. > But again as with digkim,digikam-docs,digikam-l10n, I'm not sure if it is > actually worth it to split the kipiplugins into sub-ports. > So I would suggest to simply add a single kipiplugins-kf5 port -- you may > choose to do it differently of course :). > > > mfg Tobias > > On 1 September 2016 at 02:35, Thomas Legg wrote: > >> Thanks for the feedback and link. I've updated the Created by line and >> will probably push it to github when I have some time this weekend. I'm >> also going back and looking at the makefiles for the existing kf5 ports as >> to kde:5, kde, and qt5 options >> >> I think the Makefile.common will end up staying as in many ways it seems >> to make handling the digikam-xxx-doc, digikam-xxx-l10n, the multitude of >> kipi-pluginxx ports a bit easier. Speaking of the kipi-plugin-xxx ports, >> none of these have a kde4 added to their name. Should I create new ports >> with a kf5 name (kipi-plugin-imgur-kf5)? I think I probably should as it >> looks like most of these kde4 kipi-plugins have disappeared. >> >> Thomas Legg >> >> On Tue, Aug 30, 2016 at 1:48 PM, Tobias C. Berner >> wrote: >> >>> Hi there >>> >>> Thanks a lot :) >>> >>> 1) You can modify that "Created by line" to mention you :) >>> 2) You could probably improve that Makefile a bit, by using >>> FOO_CMAKE_BOOL [1]. >>> 3) I'm personally also not a fan of the Makefile.common used in >>> digikam-kde4, >>> and now in this one too, it makes it more confusing to me [also it >>> contains kde4 bits]. >>> >>> If you wan't I can import it into plasma5/PORTS :) >>> >>> >>> mfg Tobias >>> >>> >>> [1] https://www.freebsd.org/doc/en/books/porters-handbook/makefi >>> le-options.html#options-cmake_bool >>> >>> On 29 August 2016 at 06:46, Thomas Legg wrote: >>> Would love some feedback, especially on the USES, KDE, and QT5 sections of Makefiles. https://github.com/thomaslegg/digikam-kf5 This builds digikam 5.1.0 built around a mutt version of the area51 kf5 branch. Mutt as I've rolled the kdepim back to 16.04 as 16.08 kdepim calendaring requires qt5-webengine, which seems like it's going to require a lot of work to port. If using digikam-kde4, I recommend moving the .db files out of your photo repo directories and letting digikam-kde5 build new ones. I haven't tested all of the digikam features so far, but it launches, indexes, builds thumbnails, displays photos, adds tags. More testing required and if anyone else gets this to build, I'd love feedback on your use. Thomas Legg >>> >>> >> >
[Bug 211916] [exp-run] Update Qt to 5.6.1.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211916 Raphael Kubo da Costachanged: What|Removed |Added Depends on||212349 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212349 [Bug 212349] [PATCH] editors/texstudio: Use system hunspell and quazip -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 211916] [exp-run] Update Qt to 5.6.1.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211916 --- Comment #4 from commit-h...@freebsd.org --- A commit references this bug: Author: rakuco Date: Sat Sep 3 11:45:42 UTC 2016 New revision: 421293 URL: https://svnweb.freebsd.org/changeset/ports/421293 Log: Explicitly disable C++11 during the build. Prepare for Qt 5.6, which will pass -std=gnu++11 by default when the compiler supports it, and the build currently does not work: ../libqtelegram-aseman-edition-6.1-stable/telegram/types/accountdaysttl.cpp:51:10: error: case value evaluates to 3100684255, which cannot be narrowed to type 'int' [-Wc++11-narrowing] case typeAccountDaysTTL: { Note that Qt 5.7 will start requiring C++11 support, so this will need to be fixed properly in the future. PR: 211916 Changes: head/net-im/libqtelegram-ae/Makefile -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 211916] [exp-run] Update Qt to 5.6.1.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211916 Raphael Kubo da Costachanged: What|Removed |Added Depends on||212347 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212347 [Bug 212347] [PATCH] lang/basic256: Add patch (sent upstream) to drop 'using namespace std' -- You are receiving this mail because: You are on the CC list for the bug.