Re: Messing around with linkers & CMake
On Thu, 2017-03-09 at 00:42 +0100, Adriaan de Groot wrote: > In some cases, we end up with shared-libs that are too big to include > debug > info; webkit2, webengine come to mind. Here's one way to mess with > the linking > step (bear in mind, I haven't played at *all* with the consequences > this has > nor how variable-scope affects generation). > > Consider > > add_library(foo SHARED foo.c) > > Build this in verbose mode: > cmake . > make foo VERBOSE=1 > See how the compiler is invoked at the end to link the library? > > > Now consider this: > > set(CMAKE_C_CREATE_SHARED_LIBRARY > " > > > -o ") > add_library(foo SHARED foo.c) > > This messes with the command that CMake uses -- and later expands -- > to create > shared libraries from C code; the standard definition is in > ./Modules/CMakeCInformation.cmake , and uses while > setting > the variable ourselves lets us choose the linker instead. Note that > this > *won't* compile, since the flags for the linker are seriously > different from > what the C compiler expects (in particular, you'll see -Wl,-soname in > there > where the linker invoked directly wants -soname). > > > Probably by massaging this variable in a suitable manner you can > stuff in any > particular tool you want. > > [ade] Hi, I'm interested in this because of webkitgtk. Like Adriaan said above we can't currently build it with debug support. This is not a problem on Linux because binutils have something called thin archives. I don't know anything about it apart from that it works :) So I was looking into using binutils from ports to build webkitgtk when debug is enabled. With the CMAKE_AR and CMAKE_RANLIB variables I can set the binutils ar and ranlib. However the problem is that for some reason cmake doesn't have a LINKER variable, which results in it using ld from base which doesn't understand thin archives. I tried CMAKE_LINKER a while back and that didn't seem to work. My question is now does cmake have a variable, or another way, that I can set so it uses ld from binutils instead of ld from base? -Koop
Re: [kde-freebsd] qt5-phonon4-gstreamer
So the derp I made when I committed GStreamer 1.6.0 should be fixed with the following commits. Please review when able :). gstreamer1-qt4: https://svnweb.freebsd.org/changeset/ports/398098 phonon-gstreamer: https://svnweb.freebsd.org/changeset/ports/398137 qt5-multimedia (bsd.qt.mk): https://svnweb.freebsd.org/changeset/ports/398140 qt5-phonon4-gstreamer: https://svnweb.freebsd.org/changeset/ports/398141 Cudos to Adriaan for helping track down where the problem was. -Koop On 28/09/2015 09:27, Koop Mast wrote: On 27/09/2015 22:39, Koop Mast wrote: On 27/09/2015 21:35, Adriaan de Groot wrote: (First) Patch to FindGStreamer.cmake for qt5-phonon4-gstreamer attached -- it may need a teensy bit of massaging to work in the port. It fixes the include problems caused by gstconfig.h moving out of the regular include tree. [ade] The reason for this is that gstconfig.h is now locationed outside of the normal include path there the normal gstreamer headers live. This header was moved in the 1.6.0 update. Since everyone uses pkg-config, what could possibly go wrong . right. I managed to mangle cmake in freerdp to fix the build, however the multimedia/qt5-phonon4-gstreamer multimedia/phonon-gstreamer and multimedia/gstreamer1-qt4 are beyond my cmake foo, Cudo's to Adriaan is helping with this. I'm willing to commit this, but since this is kind out of my confort zone, yes really, I would like some act from a kde@ member :) -Koop Now if they would just use pkg-config to find the correct cflags/ldflags this would not have happened, why they fuck do they want to write there own little blob of code do this /rant gstreamer1-qt4 is now fixed, I borrowed patches from OpenBSD, and there is a upstream bug too. -Koop ___ 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 ___ 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
Re: [kde-freebsd] qt5-phonon4-gstreamer
On 27/09/2015 22:39, Koop Mast wrote: On 27/09/2015 21:35, Adriaan de Groot wrote: (First) Patch to FindGStreamer.cmake for qt5-phonon4-gstreamer attached -- it may need a teensy bit of massaging to work in the port. It fixes the include problems caused by gstconfig.h moving out of the regular include tree. [ade] The reason for this is that gstconfig.h is now locationed outside of the normal include path there the normal gstreamer headers live. This header was moved in the 1.6.0 update. Since everyone uses pkg-config, what could possibly go wrong . right. I managed to mangle cmake in freerdp to fix the build, however the multimedia/qt5-phonon4-gstreamer multimedia/phonon-gstreamer and multimedia/gstreamer1-qt4 are beyond my cmake foo, Cudo's to Adriaan is helping with this. I'm willing to commit this, but since this is kind out of my confort zone, yes really, I would like some act from a kde@ member :) -Koop Now if they would just use pkg-config to find the correct cflags/ldflags this would not have happened, why they fuck do they want to write there own little blob of code do this /rant gstreamer1-qt4 is now fixed, I borrowed patches from OpenBSD, and there is a upstream bug too. -Koop ___ 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
Re: [kde-freebsd] qt5-phonon4-gstreamer
On 27/09/2015 21:35, Adriaan de Groot wrote: (First) Patch to FindGStreamer.cmake for qt5-phonon4-gstreamer attached -- it may need a teensy bit of massaging to work in the port. It fixes the include problems caused by gstconfig.h moving out of the regular include tree. [ade] The reason for this is that gstconfig.h is now locationed outside of the normal include path there the normal gstreamer headers live. This header was moved in the 1.6.0 update. Since everyone uses pkg-config, what could possibly go wrong . right. I managed to mangle cmake in freerdp to fix the build, however the multimedia/qt5-phonon4-gstreamer multimedia/phonon-gstreamer and multimedia/gstreamer1-qt4 are beyond my cmake foo, Cudo's to Adriaan is helping with this. I'm willing to commit this, but since this is kind out of my confort zone, yes really, I would like some act from a kde@ member :) -Koop Now if they would just use pkg-config to find the correct cflags/ldflags this would not have happened, why they fuck do they want to write there own little blob of code do this /rant ___ 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
Re: [kde-freebsd] [SVN Commit] branches/plasma5/KDE/sysutils
On 21-7-2015 23:38, Tobias Berner wrote: SVN commit 10934 by tcberner: new port kontactinterface-kf5-git -- blue between kpart and kontact So what is this blue your talking about, can you put it on your KDE theme? :D ___ 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
Re: [kde-freebsd] science/chemical-mime-data fails to build (convert dumping core)
On 21-10-2014 0:35, Jan Henrik Sylvester wrote:
On 10/20/2014 22:47, Raphael Kubo da Costa wrote:
Jan Henrik Sylvester m...@janh.de writes:
Trying to rebuild kde after the recent update, I could not build
science/kalzium due to science/chemical-mime-data failing:
for size in 16 22 24 32 36 48 64 72 96 128 192 ; do \
if test x != x ; then \
-w ${size} -h ${size} -f png gnome-mime-chemical.svg
gnome-mime-chemical_${size}.png ; \
else \
/usr/local/bin/convert gnome-mime-chemical.svg -resize
${size}x${size} gnome-mime-chemical_${size}.png ; \
fi \
done
Illegal instruction (core dumped)
This is on 10.0-RELEASE/amd64 with all ports up to date. Full log
attached.
It looks like it's ImageMagick's convert binary that's failing. Can you
check if it's working properly?
Thanks for your suggestion. Trying to produce a failure from a single
convert command, I found that science/chemical-mime-data builds now.
In the meantime, I had only updated a few unrelated ports and
textproc/libxml2. Maybe libxml2 was the reason.
Cheers,
Jan Henrik
Did you update the libxml2 port to the 2.9.2_1 version? That could have
fixed it because the _1 revision fixes a bug that broke the freebsd doc
chain.
-Koop
___
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
Re: [kde-freebsd] KDE doesn't build on 10-STABLE, needs WITH_NEW_XORG
On 10-3-2014 19:21, Craig Rodrigues wrote:
Hi,
Hi,
I have a 10-stable system, and I am trying to rely
as much on pkg as possible to install stuff so I don't
need to build my own packages from ports.
After the latest upgrade to KDE 4.12 in ports,
KDE does not build out of the box. It turns out
that x11/kde-workspace needs WITH_NEW_XORG.
In ports/Mk/bsd.port.mk, there is this:
# Enable new xorg for FreeBSD versions after Radeon KMS was imported unless
# WITHOUT_NEW_XORG is set.
.if ${OSVERSION} = 110
. if !defined(WITHOUT_NEW_XORG)
WITH_NEW_XORG?= yes
. else
.undef WITH_NEW_XORG
. endif
.endif
Would it be possible to bump that check to a lower value of OSVERSION?
radeonkms was imported into HEAD r254885, and this changeset
exists in stable/10.
We are working now on a patch to bump this to include 10.0-stable. The
reason why this wasn't bumped earlier was because it was deemed
unacceptable that there wasn't a console driver that could work with the
KMS driver. The infamous black screen when you started X, which stayed
black even if you quit X. Now that vt(9) was merged to 10.0-stable this
problem has been resolved, even if vt(9) isn't enabled by default yet.
I set WIT_NEW_XORG in my /etc/make.conf and rebuilt all my ports
and KDE works fine. My laptpo has a a Radeon:
(--) PCI:*(0:1:0:0) 1002:6760:103c:161e Advanced Micro Devices, Inc.
[AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] rev 0, Mem @
0xc000/268435456, 0xd440/131072, I/O @ 0x4000/256, BIOS @
0x/65536
On another note, it looks like with KDE 4.12 in ports, will there will
be no working
KDE desktop on FreeBSD-9?
Well I got some good news here, the radeonKMS driver was merged into
9.2-stable. And it being investigated/worked on to get vt(9) also merged
into the 9.2-stable branch. So we can switch to the new Xorg version
there too.
-Koop
--
Craig
___
freebsd-po...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
___
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
Re: [kde-freebsd] [SVN Commit] area51/KDE/x11/kde4-workspace
On 10-2-2014 8:42, Max Brazhnikov wrote: Is there any progress? Shall I disable gles if WITH_GALLIUM is set? I want to commit KDE ports this week. No progress, sorry. What time I had got nuked by a case of seasonal flu strike -Koop ___ 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
Re: [kde-freebsd] KDE 4.12 and WITH_NEW_XORG=no
On 28-1-2014 10:11, Raphael Kubo da Costa wrote: As we're finally close to getting the 4.12.1 ports into a reasonable stable where everything builds, I'd like to start discussing merging area51 back into ports -- we've already skipped the whole 4.11 release cycle. As I see it, the biggest question is what to do with WITH_NEW_XORG=no: kde4-workspace will not build with the ancient version of Mesa that gets build when WITH_NEW_XORG is disabled. And FreeBSD's pkg building cluster does not enable this variable on its 8- and 9- builds, which mean we wouldn't get part of the KDE packages built for those releases at all. Just a note with my x11@ hat on: As you probably know WITH_NEW_XORG is default on HEAD. The current plan is to enable this on 10-stable in time for 10.1-R but that depends on if vt(9) is merged by then. There is currently no reason to believe this won't happen. -Koop ___ 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
Re: [kde-freebsd] KDE 4.12 and WITH_NEW_XORG=no
On 28-1-2014 10:52, Schaich Alonso wrote: On Tue, 28 Jan 2014 07:11:32 -0200 Raphael Kubo da Costa rak...@freebsd.org wrote: As we're finally close to getting the 4.12.1 ports into a reasonable stable where everything builds, I'd like to start discussing merging area51 back into ports -- we've already skipped the whole 4.11 release cycle. As I see it, the biggest question is what to do with WITH_NEW_XORG=no: kde4-workspace will not build with the ancient version of Mesa that gets build when WITH_NEW_XORG is disabled. And FreeBSD's pkg building cluster does not enable this variable on its 8- and 9- builds, which mean we wouldn't get part of the KDE packages built for those releases at all. ___ 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 Hi In a mail to stable@ which was not replied so far, ama...@li.ru reported on 2014-01-22 that he can't build even cairo (poppler) without WITH_NEW_XORG, which both are dependecies to KDE4. I have no setup to verify this breakage at the moment, though should this be true it means we have a broken default setup on FreeBSD 8, 9 and 10. Alonso As maintainer of both, I can say that I'm not aware of any problems with either port. I will check the mail report and see if I can find out where that breakage comes from. -Koop ___ 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
Re: [kde-freebsd] ports/181921: [exp-run] Update Qt to 4.8.5
On 9-10-2013 22:02, Max Brazhnikov wrote: On Wed, 09 Oct 2013 17:18:50 + Max Brazhnikov wrote: On Tue, 01 Oct 2013 06:27:24 -0500 Bryan Drewery wrote: Failures: http://package19.nyi.freebsd.org/bulk/91amd64-default-pr_181921/2013-09-30_10h40m38s/logs/errors/qcad-3.2.1.0.log I'm looking on how to fix it. The tarball ships pregenerated bindings for several Qt versions, and 4.8.5 is not among them. http://people.freebsd.org/~makc/patches/qcad.diff Cheers, Max This has no impact on the patch test but Where you sure to nuke the second line in the DESKTOP_ENTRIES. The one with the description? -Koop ___ 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
Re: [kde-freebsd] py27-pykde4-4.10.1
On 30-3-2013 11:59, Alberto Villa wrote: On Saturday 30 March 2013 05:44:36 ajtiM wrote: Port p27-pykde4-4.10.1 (and previous versions too) has a problem with pop-up menus during installation: When I run installation with portmaster I setup options, before building it asked me for settings again and before installation it asked me again. I have a problem just with this port. It's a problem with new OPTIONS implementation (PKGNAMEPREFIX is used before being defined), it affects many other ports too. I'll see how this can be fixed globally. FYI http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148637 ___ 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
Re: [kde-freebsd] kde4-workspace build problem
On 1-2-2013 20:18, Schaich Alonso wrote: Actually, a fix was already commited to the ports repository by bapt@ two hours ago (r311389) What about area51? Does the port is in area51 does it still refer to the old boost lib? -Koop On 2013-02-01 10:08, Derrick Dantavious Edwards wrote: Hi, I continue to have problems building kde4-workspace I get the following error. === Running ldconfig /sbin/ldconfig -m /usr/local/lib === Registering installation for boost-libs-1.52.0 as automatic Installing boost-libs-1.52.0... done === Returning to build of kde-workspace-4.8.4 Error: shared library boost_thread.4 does not exist *** [lib-depends] Error code 1 Stop in /usr/ports/x11/kde4-workspace. *** [reinstall] Error code 1 boost-libs installed these find /usr/local/ -iname *boost_thread* -print /usr/local/lib/libboost_thread.a /usr/local/lib/libboost_thread.so.5 /usr/local/lib/libboost_thread.so /usr/local/lib/compat/pkg/libboost_thread.so.4 Any ideas? Derrick ___ 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 ___ 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 ___ 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
Re: [kde-freebsd] Unable to build deskutils/kdepimlibs4
On 5-1-2013 2:17, Adriaan de Groot wrote: On Friday, January 04, 2013 07:24:28 PM Jerry wrote: Following the directions in UPDATING, I used the following command: portupgrade -fr devel/libical That port updated correctly; however, the next port: The entire build log is available here: https://www.seibercom.net/logs/kdep.txt I do not see an obvious reason for the build failure. I tried it three times including doing a distclean and updating the ports tree. There is an obvious reason, but you have to scroll back a ways in the log: /usr/ports/deskutils/kdepimlibs4/work/kdepimlibs-4.8.4/kioslave/smtp/command.cpp In file included from /usr/ports/deskutils/kdepimlibs4/work/kdepimlibs-4.8.4/kioslave/smtp/command.h:37, from /usr/ports/deskutils/kdepimlibs4/work/kdepimlibs-4.8.4/kioslave/smtp/command.cpp:32: /usr/local/include/sasl/sasl.h:228: error: typedef 'sasl_malloc_t' is initialized (use __typeof__ instead) /usr/local/include/sasl/sasl.h:228: error: 'size_t' was not declared in this scope This is because of the new sasl port, which does not include all the headers it needs in its own headers (e.g. defining size_t). You can patch /usr/local/include/sasl/sasl.h to fix that, or patch command.cpp to #include the right headers before sasl.h. [ade] Currect, however it was fixed in rev 309488 8 days ago in the sasl port itself. So other hacks are not needed anymore. I suspect Jerry needs to update his cyrus-sasl port and maybe even his ports tree if the fix isn't there. http://svnweb.freebsd.org/ports/head/security/cyrus-sasl2/Makefile?view=log ___ 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
Re: [kde-freebsd] pcre bump
On 13-12-2012 12:05, Alberto Villa wrote: I see it was done by mm@; or were you referring to area51? I was referring to area51 yes. I helped a user yesterday in #kde-freebsd that ran into kdelibs4 looking for the wrong pcre lib. ___ 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
[kde-freebsd] pcre bump
Hello alberto, Could you chase the pcre lib_depend line in x11/kdelibs4/Makefile? it is currently stuck at .1 while the port was recently updated and it installs .3. -Koop ___ 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
Re: [kde-freebsd] Qt 5
On 30-11-2012 13:52, Alberto Villa wrote: Qt 4 is now building fine along with Qt 5. There is still this conflict with *.pc files, I'll take care of it. I think this is nuts, if these pkg-config files are shipped by upstream, upstream should version them. If they don't do that and we need to do it, then everything that finds QT5 with pkg-config (which might not me a lot) needs to be patched :/. That or QT5 is a drop in replacement of QT4, and looking at my experiance with GTK+ that probably not true. -Koop ___ 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
Re: [kde-freebsd] [SVN Commit] branches/qt-5.0/QT/Mk
On 24-11-2012 11:01, Alberto Villa wrote: SVN commit 8734 by avilla: - Disable accessibility, as -no-xcb causes it to be built for non-Unix platforms. It depends on AT-SPI 2, which seems to not be completely ported yet. We got version 2.6.0 in MC, will that do? Might not be completely bug free yet.. -Koop ___ 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
Re: [kde-freebsd] [SVN Commit] branches/qt-5.0/QT/Mk
On 24-11-2012 12:34, Alberto Villa wrote: On Sat, Nov 24, 2012 at 12:03 PM, Koop Mast k...@rainbow-runner.nl wrote: - Disable accessibility, as -no-xcb causes it to be built for non-Unix platforms. It depends on AT-SPI 2, which seems to not be completely ported yet. We got version 2.6.0 in MC, will that do? Might not be completely bug free yet.. Don't know yet. Does it install a pkg-config file and some headers? Do you really check our commit logs? :) The 2.6 version does install pkg-config stuff. I needed it for gtk-3.. I don't read the actual commits, just lurking on the mailing list :) -Koop ___ 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
Re: [kde-freebsd] [SVN Commit] area51/KDE/misc/kdeedu4
On Thu, 2011-10-20 at 12:04 +, Max Brazhnikov wrote: On Thu, 20 Oct 2011 04:34:45 -0700 (PDT), Raphael Kubo da Costa wrote: SVN commit 7750 by rakuco: kdeedu4: Experiment with disabling kalzium by default. It depends on avogadro and will pull in GCC from ports, which might be overkill for most users. Guys, what do you think? I was always wondering why people install x11/kde4 instead of installing kdebase* ports and choosing what they need from other ports. Maybe we should disable all options in x11/kde4 or create x11/kde4-minimum? Max That last option is what we do in gnome. We got x11/gnome2 which installs all the gnome 2 desktop bits and pieces. And we got x11/gnome2-lite which installs the bare minimum needed to get a gnome desktop running. And no it doesn't install gdm/epiphany. -Koop ___ 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
Re: [kde-freebsd] dependencies
On Thu, 2011-10-13 at 11:42 +0200, Olivier Smedts wrote: 2011/10/13 Alberto Villa avi...@freebsd.org: A long (long) time ago... On Sun, May 22, 2011 at 9:46 AM, Schaich Alonso alonsoscha...@gmx.de wrote: *when using WITH_DEBUG, deskutils/strigi should depend on devel/cppunit Will look into this. Or did you do it already, rakuco? *devel/kdevplatform should not depend on multimedia QT_COMPONENTS rakuco applied it. *x11/kdebase4-runtime and multimedia/kdemultimedia4 should probably only depend on multimedia/xine if the later was selected as OPTION for x11/kde4 Well, yes. Actually, there's no xine option anymore, as phonon-xine is deprecated. I think i'll make it optional, or a separate port, or whatever. I still use it as my main phonon backend. That's the only one just working, correctly. vlc backend is buggy as hell and makes phonon crash, and gstreamer backend installs too much cr... dependencies. And ^^ Heh, I hear you :). The issue is that vlc/xine is one package with all you need. The Gstreamer framework is basic functionality and you install plugins for support that you need. I admit it is a bit of a hassle, and maintainers need to make a choice what they want to include. If you run into any gstreamer stuff that has added baggage that they don't need, let me know :) -Koop it doesn't read the flac files I can read with the xine backend (default gstreamer install as a dependency, no special plugins installed). Nothing technical here, just saying xine backend is still a good option :) ___ 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
[kde-freebsd] Re: [ANNOUNCE]: clang compiling ports
On 30-6-2011 14:42, Alberto Villa wrote: On Mon, Jun 20, 2011 at 5:37 PM, Roman Divackyrdiva...@freebsd.org wrote: It would be great if you could skim over the list to see if some of the ports you maintain are broken and possibly try to fix them. as of today, qt 4 builds successfully with clang :) A small introduction into the Clang+Ports can be read at: http://wiki.freebsd.org/PortsAndClang. i read that you have patches for bsd.qt.mk. we imported support for clang months ago, but if you still have any patches, please, send them to k...@freebsd.org I need to review the patches mentioned on the end of that wiki page. But I have currently a couple of deadlines I need to do work for, so that takes priority atm. If I find anything that is still needed, I will let the responsible people now. -Koop Thank you for helping us! thank you for the work on clang! ___ 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
[kde-freebsd] Re: Gnome3 on powerpc, KDE4 on powerpc
On Fri, 2011-03-25 at 13:10 -0400, Super Bisquit wrote: gobject-introspection is 0.10.4 for gnome3. I don't see how this is a problem, can you explain it in more detail? py-gstreamer is at 0.10.21 on ports and 0.10.20 on marcusports Fixed, by removing the MC version. Thanks for the notice. marcusports has gtk3 applications while kde4 still uses gtk2 Well apart from the gnome desktop stuff, pure gtk2 and gtk3 applications can just live together with no problem. There are a few exceptions but most should just work. Not that gtk2 will be alround for a long time to come, just look at gtk12 :) -Koop These are the first few. On 3/25/11, Alberto Villa avi...@freebsd.org wrote: On Friday 25 March 2011 15:43:18 Super Bisquit wrote: Whatever dependencies that each has in common needs to be updated to the most recent. If gnome3 has the most recent, then use those. If kde4 has the most recent, use those. do you have an idea of which dependencies do conflict? I am very glad and thankful that I am allowed to work with and on both teams and would like to remain doing so. thank you for your effort. i hope we'll be able to reach some results! -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla Your lucky color has faded. ___ 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
