[kde] Re: Building DBusMenu-Qt
David Doria posted on Fri, 17 Jun 2011 22:28:59 -0400 as excerpted: > I am on RHEL 5.6 which has super old packages of everything. I have > therefore built Qt from source and am building kdelibs from source. So > my question is more of "why did qdbusxml2cpp not get built when I built > Qt?". Is there a way to "enable everything" or something like that? I'm > so used to cmake now-a-days that I don't know how to set options like > that without it! 5.6. Yeah, that'd be older packages, for sure. Why didn't qdbusxml2cpp get built with qt? I don't know as the gentoo build-scripts have always taken care of that for me. Are you sure it did /not/ get built? Here, it's in /usr/bin, but presumably it'd be in /usr/local/bin or the like if you didn't specify a location for it. Maybe your dbus is too old? Let's see what the deps look like for it. I have dbus-1.4.12 installed. The qt-dbus ebuild requires >=dbus-1.0.2. Gentoo's dbus versions go back only thru 1.4.6, which was introduced only in February of this year. dbus-1.0.2 appears to have been introduced in Gentoo back in Dec of 2006 and removed in July of 2009. Meanwhile, the configure logs spit this out when testing for dbus: D-Bus auto-detection... () And the summary at the end of the configure step includes this: QtDBus module .. yes (linked) So try searching/grepping for that in your qt build log and see what turns up. (Or if that's gone, you can just run thru the configure step and see what it spits out. That's what I just did here as I only keep ~4 weeks of build-log rotation and qt-4.7.3 was installed ~5-6 weeks ago.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: Building DBusMenu-Qt
> I believe the executable you are looking for is qdbusxml2cpp, which is > part of the package (on gentoo) qt-dbus, which in turn is a part of qt, > split-packaged on gentoo as qt-core, qt-dbus, qt-declarative... and a > bunch of others. > > So you either need qt installed, or a newer version installed, or to tell > cmake where to find it, I don't know which. I am on RHEL 5.6 which has super old packages of everything. I have therefore built Qt from source and am building kdelibs from source. So my question is more of "why did qdbusxml2cpp not get built when I built Qt?". Is there a way to "enable everything" or something like that? I'm so used to cmake now-a-days that I don't know how to set options like that without it! David ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: Building DBusMenu-Qt
David Doria posted on Fri, 17 Jun 2011 17:25:04 -0400 as excerpted: > Following the instructions here: > http://techbase.kde.org/Getting_Started/Build/Qt#DBusMenu-Qt > > I cloned DBusMenu-Qt . Then I ran cmake, it says: > > "Please set them or make sure they are set and tested correctly in the > CMake files: > QT_QTDBUS_INCLUDE_DIR (ADVANCED)" > > However, it lets me generate anyway. Then when I run 'make', I get: > > [ 3%] Generating dbusmenuadaptor.cpp, dbusmenuadaptor.h /bin/sh: > QT_DBUSXML2CPP_EXECUTABLE-NOTFOUND: command not found > > I searched for find . -iname *xml2cpp* > in my /home/ddoria/bin/qt4, but it didn't find anything. > > Am I missing something in this process? I believe the executable you are looking for is qdbusxml2cpp, which is part of the package (on gentoo) qt-dbus, which in turn is a part of qt, split-packaged on gentoo as qt-core, qt-dbus, qt-declarative... and a bunch of others. So you either need qt installed, or a newer version installed, or to tell cmake where to find it, I don't know which. FWIW, I have qt-4.7.3 installed here. All available libdbusmenu-qt versions (0.8.2, 0.6.2, and a live-build version I didn't mention earlier, live-builds are fake-versioned on gentoo as for those brave enough to unmask and try them) on gentoo require qt version 4.6.3 minimum. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Building DBusMenu-Qt
Following the instructions here: http://techbase.kde.org/Getting_Started/Build/Qt#DBusMenu-Qt I cloned DBusMenu-Qt . Then I ran cmake, it says: "Please set them or make sure they are set and tested correctly in the CMake files: QT_QTDBUS_INCLUDE_DIR (ADVANCED)" However, it lets me generate anyway. Then when I run 'make', I get: [ 3%] Generating dbusmenuadaptor.cpp, dbusmenuadaptor.h /bin/sh: QT_DBUSXML2CPP_EXECUTABLE-NOTFOUND: command not found I searched for find . -iname *xml2cpp* in my /home/ddoria/bin/qt4, but it didn't find anything. Am I missing something in this process? Thanks, David ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: Building kdelibs
David Doria posted on Fri, 17 Jun 2011 13:10:55 -0400 as excerpted: > Duncan, > > I am on RHEL. I am getting this when configuring kdelibs using > kdesrc-build: > > CMake Error: The following variables are used in this project, but they > are set to NOTFOUND. > Please set them or make sure they are set and tested correctly in the > CMake files: > DBUSMENUQT_INCLUDE_DIR (ADVANCED) >used as include directory in directory >/home/ddoria/kdesrc/kdelibs/kdeui snip... > DBUSMENUQT_LIBRARIES (ADVANCED) > linked by target "kdeui" in directory > /home/ddoria/kdesrc/kdelibs/kdeui > > I installed dbus* but that didn't seem to help. There is a separate (at least on gentoo) package libdbusmenu-qt. The gentoo dep for kdelibs-4.6.4 is >=libdbusmenu-qt-0.3.2 , but I have 0.8.2, far newer (introduced to gentoo in April according to the gentoo changelog). The other available gentoo version is 0.6.2, from Sept. 2010, so even it's not that old. The changelog records a large version jump between 0.3.5 in June, 2010 and 0.6.2, with 0.3.2 from April of 2010, removed in Sept. So if you're on RHEL 6, you may have a reasonable version available, but may need to find a newer version to meet the 0.3.2 requirement if you're on RHEL 5.x, since 0.3.2 is only a bit over a year old, at least by Gentoo introduction time. Of course as you're probably already aware, RHEL being a binary distro often splits the build-time and runtime bits of libraries into separate packages (something I've been very happy to forget about on gentoo, where it wouldn't make much sense anyway since it's from-source and the build- time bits therefore necessary if the library is, in any case), so you'll likely need both the main library package and the -devel package. Hope that helps. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: Building kdelibs
> FWIW, I'm a Gentooer. Gentoo builds from source using buildscripts > called ebuilds that list required dependencies and handle optional > dependencies using what Gentoo calls USE flags. > > As a result, I've been able to help a number of people trying to build kde > manually by simply querying the Gentoo build system for kde's various > dependencies. One guy (James Tyrer) in particular runs Linux from > Scratch, and builds KDE for it as updates come out, updating their KDE > documentation for others as he does so. I've been able to help him > resolve missing dependencies on a number of occasions. > > That leaves you with a number of potentially useful resources to choose > from. Of course you could switch to Gentoo if you like, and get most of > the building automated thru the various scripts without losing a whole > lot since they still expose most of the build-time options as USE flags. > But even if you're not doing Gentoo, you can either post questions here > and I can check dependencies, or you could download a Gentoo build tree > and check them yourself, or simply check their sources on the web. > > Alternatively and probably easier to follow as the basics will already > have been distilled into a reasonably nice set of instructions to follow, > you can find and follow the LFS kde building instructions as maintained > by James Tyrer, with the caveat that as every minor version (4.5, 4.6, > 4.7...) comes out, it takes some days/weeks for their build instructions > to be fully updated. > > FWIW, the gentoo/kde project has live builds that they try to keep in > sync with kde upstream, so most of the updates are already understood > when an update comes out, it's just a matter of actually transferring > them from the live build scripts to the specific version scripts. Given > that kde makes the new tarballs available to the various distributions > several days before public release, by public release, the scripts are > generally already updated in the gentoo/kde project overlay, which I > follow, and moved to the general kde tree within another week or so after > final testing... kde sometimes updates one of the tarballs after release > to the distributions so the final checksums need to be updated, etc. So > they move to the general kde tree pretty fast, tho unmasking to arch- > testing can take a bit longer and moving to full stable can take months > -- they just stabilized 4.6.2, before which the latest gentoo kde stable > was 4.4.5, IIRC. But the initial masked-for-testing ebuilds are > generally in the gentoo/kde overlay before upstream public release, and > in the main gentoo tree within days of release. > > James, the LFS guy, doesn't appear to follow the pre-releases or live- > builds, so he's typically some days to weeks behind Gentoo's move of the > build-scripts to the general tree. I believe he tends to finally get the > 4.x.0 instructions up about time kde upstream 4.x.1 comes out a month > later. But after the initial minor-release update, the rest in the > series are far easier as they're much smaller bumps with far fewer > changes. So in general, 4.x.1 thru 4.x.5 can continue to use the 4.x.0 > instructions. It's only with the bump to 4.y.0 that serious changes > occur, forcing changes to the LFS build instructions that again take a > month, perhaps six weeks, to work their way thru. > > So... if you'd like me to post the gentoo dependency list for kdelibs, > let me know. As I said, such things have helped James and occasionally > others work out dependencies for their builds, occasionally. Or you can > look them up yourself, checking the gentoo/kde public sources, but it > might take a bit of extra digging to figure out the notation they use. > > -- > Duncan > > Duncan, I am on RHEL. I am getting this when configuring kdelibs using kdesrc-build: CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: DBUSMENUQT_INCLUDE_DIR (ADVANCED) used as include directory in directory /home/ddoria/kdesrc/kdelibs/kdeui used as include directory in directory /home/ddoria/kdesrc/kdelibs/kdeui/about used as include directory in directory /home/ddoria/kdesrc/kdelibs/kdeui/tests used as include directory in directory /home/ddoria/kdesrc/kdelibs/kdeui/tests/kconfig_compiler used as include directory in directory /home/ddoria/kdesrc/kdelibs/kdeui/tests/proxymodeltestsuite used as include directory in directory /home/ddoria/kdesrc/kdelibs/kdeui/tests/proxymodeltestapp used as include directory in directory /home/ddoria/kdesrc/kdelibs/kdeui/sonnet/tests DBUSMENUQT_LIBRARIES (ADVANCED) linked by target "kdeui" in directory /home/ddoria/kdesrc/kdelibs/kdeui I installed dbus* but that didn't seem to help. Any thoughts? David ___ This message is from the kde mailing list. Account management: https://mail
[kde] Re: KDE secretly on TV
Am 17.06.2011 18:09, schrieb Steven Sroka: > True, but that is a picture of Leonard:) > Leonard seems to be a KDE man! > > I wonder if Leonard and Sheldon ever duke it out? Should be into the next season ;D > Leonard vs Sheldon > KDE vs Gnome -- Kim Leyendecker k...@k-dl.de.vu openSUSE Ambassador, openSUSE Wiki DE Send from my notebook ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: KDE secretly on TV
>On 17 June 2011 10:33, Kim Leyendecker wrote: > Am 16.06.2011 10:50, schrieb Rafa Griman: >> Do you watch "The Big Bang Theory"? ... H, dumb question, you >> say: "I love being a nerd" ... that implies you do, just like me;) >> > > But I think Sheldon love Ubuntu? So he should use GNOME!? ;-) True, but that is a picture of Leonard :) Leonard seems to be a KDE man! I wonder if Leonard and Sheldon ever duke it out? Leonard vs Sheldon KDE vs Gnome > > A KDE shirt? cool thing, but in general, there using Windows on their > computers. According to Sheldon: "My new computer came with WIndows 7. > It´s much more user friendly then Windows Vista. I don´t like that" > > -kdl > > -- > Kim Leyendecker (k...@k-dl.de.vu) > openSUSE Ambassador, openSUSE Wiki Team DE > HAVE A LOT OF FUN! > http://www.opensuse.org > Have you tried SUSE Studio? Need to create a Live CD, an app you want > to package and distribute or create your own Linux distro. Give SUSE > Studio a try. http://www.susestudio.com > > ___ > This message is from the kde mailing list. > Account management: https://mail.kde.org/mailman/listinfo/kde. > Archives: http://lists.kde.org/. > More info: http://www.kde.org/faq.html. > ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: Building kdelibs
David Doria posted on Fri, 17 Jun 2011 08:44:54 -0400 as excerpted: > I am trying to build kdelibs. I ran cmake, and it told me that I needed > Automoc4 (part of KDE Support). I built automoc, and then it said I > needed Phonon (also part of KDE Support). Is there a way to build all of > KDE Support without doing it one package at a time? I see on this page: > http://techbase.kde.org/Getting_Started/Build/KDE_Support that it says > they are separate modules and should be bulit separately, but isn't this > quite an involved process just to build a prerequisite for kdelibs? Can > you please just let me know if I am going about it correctly? FWIW, I'm a Gentooer. Gentoo builds from source using buildscripts called ebuilds that list required dependencies and handle optional dependencies using what Gentoo calls USE flags. As a result, I've been able to help a number of people trying to build kde manually by simply querying the Gentoo build system for kde's various dependencies. One guy (James Tyrer) in particular runs Linux from Scratch, and builds KDE for it as updates come out, updating their KDE documentation for others as he does so. I've been able to help him resolve missing dependencies on a number of occasions. That leaves you with a number of potentially useful resources to choose from. Of course you could switch to Gentoo if you like, and get most of the building automated thru the various scripts without losing a whole lot since they still expose most of the build-time options as USE flags. But even if you're not doing Gentoo, you can either post questions here and I can check dependencies, or you could download a Gentoo build tree and check them yourself, or simply check their sources on the web. Alternatively and probably easier to follow as the basics will already have been distilled into a reasonably nice set of instructions to follow, you can find and follow the LFS kde building instructions as maintained by James Tyrer, with the caveat that as every minor version (4.5, 4.6, 4.7...) comes out, it takes some days/weeks for their build instructions to be fully updated. FWIW, the gentoo/kde project has live builds that they try to keep in sync with kde upstream, so most of the updates are already understood when an update comes out, it's just a matter of actually transferring them from the live build scripts to the specific version scripts. Given that kde makes the new tarballs available to the various distributions several days before public release, by public release, the scripts are generally already updated in the gentoo/kde project overlay, which I follow, and moved to the general kde tree within another week or so after final testing... kde sometimes updates one of the tarballs after release to the distributions so the final checksums need to be updated, etc. So they move to the general kde tree pretty fast, tho unmasking to arch- testing can take a bit longer and moving to full stable can take months -- they just stabilized 4.6.2, before which the latest gentoo kde stable was 4.4.5, IIRC. But the initial masked-for-testing ebuilds are generally in the gentoo/kde overlay before upstream public release, and in the main gentoo tree within days of release. James, the LFS guy, doesn't appear to follow the pre-releases or live- builds, so he's typically some days to weeks behind Gentoo's move of the build-scripts to the general tree. I believe he tends to finally get the 4.x.0 instructions up about time kde upstream 4.x.1 comes out a month later. But after the initial minor-release update, the rest in the series are far easier as they're much smaller bumps with far fewer changes. So in general, 4.x.1 thru 4.x.5 can continue to use the 4.x.0 instructions. It's only with the bump to 4.y.0 that serious changes occur, forcing changes to the LFS build instructions that again take a month, perhaps six weeks, to work their way thru. So... if you'd like me to post the gentoo dependency list for kdelibs, let me know. As I said, such things have helped James and occasionally others work out dependencies for their builds, occasionally. Or you can look them up yourself, checking the gentoo/kde public sources, but it might take a bit of extra digging to figure out the notation they use. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: KDE secretly on TV
Am 16.06.2011 10:50, schrieb Rafa Griman: > Do you watch "The Big Bang Theory"? ... H, dumb question, you > say: "I love being a nerd" ... that implies you do, just like me;) > But I think Sheldon love Ubuntu? So he should use GNOME!? ;-) A KDE shirt? cool thing, but in general, there using Windows on their computers. According to Sheldon: "My new computer came with WIndows 7. It´s much more user friendly then Windows Vista. I don´t like that" -kdl -- Kim Leyendecker (k...@k-dl.de.vu) openSUSE Ambassador, openSUSE Wiki Team DE HAVE A LOT OF FUN! http://www.opensuse.org Have you tried SUSE Studio? Need to create a Live CD, an app you want to package and distribute or create your own Linux distro. Give SUSE Studio a try. http://www.susestudio.com ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: Building kdelibs
> > You probably need some policykit development packages. > If you don't plan on using the KAuth features in your build, you can also > just > ignore this (its just a warning after all). > It says "warning", but after configuring multiple times it never gives me the "generate" option in ccmake :( > Seems you are missing one of the Perl addon packages. > On Debian this would be libxml-parser-perl Great. For anyone else reading the package on RHEL was called perl-libxml-perl. However, now at the end of my: ./kdesrc-build --pretend I see: <<< PACKAGES FAILED TO BUILD >>> qt-copy Is that just because the --pretend told it not to download/build? Nothing appears to be out of order in the output related to qt-copy: Building qt-copy (1/43) Waiting for source code update. Source update complete for qt-copy: 1 file affected. Unknown build system for qt-copy (is it supposed to be built at all?) Would have created /home/ddoria/kdesrc/build Preparing build system for qt-copy. Would have cleaned build system for qt-copy Would have created /home/ddoria/kdesrc/build/qt-copy Overall time for qt-copy was 0 seconds. Should I proceed without the --pretend? Thanks, David ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: Building kdelibs
On Friday, 2011-06-17, David Doria wrote: > On Fri, Jun 17, 2011 at 8:56 AM, David Doria wrote: > >> Check http://kdesvn-build.kde.org/ > >> > >> Nice tool for building KDE and its main dependencies directly for the > >> repositories. > >> > >> Cheers, > >> Kevin > > Also, I tried kdesrc-build. I copied the kdesrc-buildrc-sample to > ~/.kdesrc-buildrc, and then ran: > > ~/src/kdesrc-build-1.13$ ./kdesrc-build --pretend > Can't locate XML/Parser.pm in @INC (@INC contains: > /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi > /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl > /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi > /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl > /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 > .) at ./kdesrc-build line 443. > BEGIN failed--compilation aborted at ./kdesrc-build line 443. > > Thoughts? Seems you are missing one of the Perl addon packages. On Debian this would be libxml-parser-perl Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: Building kdelibs
On Friday, 2011-06-17, David Doria wrote: > > Check http://kdesvn-build.kde.org/ > > > > Nice tool for building KDE and its main dependencies directly for the > > repositories. > > > > Cheers, > > Kevin > > Thanks Kevin, I will try that. If I wanted to proceed manually, I have > a new problem. After building automoc and phonon and setting the > approriate paths in the kdelibs cmake, I am getting (when > configuring): > > WARNING: No valid KAuth backends will be built. The library will not work > properly unless compiled with a working backend > > How would I fix that? You probably need some policykit development packages. If you don't plan on using the KAuth features in your build, you can also just ignore this (its just a warning after all). Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: Building kdelibs
On Fri, Jun 17, 2011 at 8:56 AM, David Doria wrote: >> Check http://kdesvn-build.kde.org/ >> >> Nice tool for building KDE and its main dependencies directly for the >> repositories. >> >> Cheers, >> Kevin Also, I tried kdesrc-build. I copied the kdesrc-buildrc-sample to ~/.kdesrc-buildrc, and then ran: ~/src/kdesrc-build-1.13$ ./kdesrc-build --pretend Can't locate XML/Parser.pm in @INC (@INC contains: /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at ./kdesrc-build line 443. BEGIN failed--compilation aborted at ./kdesrc-build line 443. Thoughts? David ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: Building kdelibs
> Check http://kdesvn-build.kde.org/ > > Nice tool for building KDE and its main dependencies directly for the > repositories. > > Cheers, > Kevin Thanks Kevin, I will try that. If I wanted to proceed manually, I have a new problem. After building automoc and phonon and setting the approriate paths in the kdelibs cmake, I am getting (when configuring): WARNING: No valid KAuth backends will be built. The library will not work properly unless compiled with a working backend How would I fix that? Thanks, David ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Re: Building kdelibs
On Friday, 2011-06-17, David Doria wrote: > I am trying to build kdelibs. I ran cmake, and it told me that I > needed Automoc4 (part of KDE Support). I built automoc, and then it > said I needed Phonon (also part of KDE Support). Is there a way to > build all of KDE Support without doing it one package at a time? I see > on this page: http://techbase.kde.org/Getting_Started/Build/KDE_Support > that it says they are separate modules and should be bulit separately, > but isn't this quite an involved process just to build a prerequisite > for kdelibs? Can you please just let me know if I am going about it > correctly? Check http://kdesvn-build.kde.org/ Nice tool for building KDE and its main dependencies directly for the repositories. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part. ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
[kde] Building kdelibs
I am trying to build kdelibs. I ran cmake, and it told me that I needed Automoc4 (part of KDE Support). I built automoc, and then it said I needed Phonon (also part of KDE Support). Is there a way to build all of KDE Support without doing it one package at a time? I see on this page: http://techbase.kde.org/Getting_Started/Build/KDE_Support that it says they are separate modules and should be bulit separately, but isn't this quite an involved process just to build a prerequisite for kdelibs? Can you please just let me know if I am going about it correctly? Thanks, David ___ This message is from the kde mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.
