Sorry to post two in a row.
I was trying to resolve my Nepomuk issue not finding any provider, so I figure, remove Strigi since it is not required anymore, and try to directly integrate versions of rasqal, librdf and raptor into my build process since my kde4 is not in a standard location (/opt/kde4) as t onot overwrite my existing RHEL 6.4 KDE 4.3.

in my .kdesrc-buildrc, I have the following for the modules..
module rasqal
repository git://github.com/dajobe/rasqal.git
branch master
end module

module raptor
repository git://github.com/dajobe/raptor.git
branch master
end module

module librdf
repository git://github.com/dajobe/librdf.git
branch master
end module

when I run ./kdesrc-build --refresh-build rasqal raptor librdf they retrieve the modules, but they do not compile. The problem I found is not that they do not have a compatible build system, they use autogen.sh, but it is how kdesrc-build seems to be calling it.

If I look at the configure.log from rasqal, I see the following:
kdesrc-build running: '/home/ntruhan/kdesrc/rasqal/autogen.sh' '--prefix=/opt/kde4'
# from directory: /home/ntruhan/kdesrc/build/rasqal
autogen.sh: Looking for programs: automake aclocal autoconf autoheader libtoolize
autogen.sh: automake program 'automake' V 011106 (min 011102) in /usr/bin
autogen.sh: aclocal program 'aclocal' V 011106 (min 011102) in /usr/bin
autogen.sh: autoconf program 'autoconf' V 026800 (min 026200) in /usr/bin
autogen.sh: autoheader program 'autoheader' V 026800 (min 026200) in /usr/bin
autogen.sh: libtoolize program 'libtoolize' V 020210 (min 020200) in /usr/bin
autogen.sh: Dependencies satisfied

autogen.sh: Running ./configure --enable-maintainer-mode --prefix=/opt/kde4
/home/ntruhan/kdesrc/rasqal/autogen.sh: line 422: ./configure: No such file or directory

It is being run from the build directory, and If I try to execute /home/ntruhan/kdesrc/rasqal/autogen.sh --prefix=/opt/kde4 manually from the build directory it hangs there. BUT if I run that command line from the /home/ntruhan/kdesrc/rasqal directory, it generates a valid ./configure file, executes it which is successfull and waits for the make to be run.

Is this perhaps something to do with me calling it from an external repository? or it using autogen instead of CMake? If there was something to get it to run from the kdesrc/rasqal directory, perhaps that would work.

I am doing this fine with another module form github, the libmygpo-qt module and that works fine and builds into the system.

Does someone have a suggestion for this? Perhaps a kdesrc-build flag I might be overlooking to send it to the kdesrc directory instead of build?

Thanks in advance.

I've checked with the author of kdesrc-build and unfortunately in this instance you have run into a bug in autogen / automake.
He suggested either running the installation of those three components manually, or attempting to use custom-build-command option to invoke a personal script which will handle this properly.

See http://kdesrc-build.kde.org/documentati ... ld-command for more information on that kdesrc-build option.

Yes, the problem in this case is that raptor, rasqal, etc. don't seem to support building from a directory other than the source directory. kdesrc-build always builds from a separate directory to make it possible to easily remove the build directory as needed.

The reason it doesn't work may be related to the autogen.sh included with the source code, or it may be because the local "autotools" components on the computer where you are trying to run the build have bugs with this support (possibly even both).

If you just want to do a one-time build it's probably easiest to just manually build and install from the source directory, or try to fool kdesrc-build into setting the same build-dir and source-dir for the 3 modules that are affected. N.B.: if this breaks you get to keep all the pieces .

Alternately you can make up a custom shell script and use that in conjunction with the custom-build-command option.

(I'm the kdesrc-build author, in case you're wondering)

Thank you for the help.
WIth that, I was able to get those to compile along with virtuoso, so now Nepomuk is working!

module rasqal
repository git://github.com/dajobe/rasqal.git
branch master
build-dir ~/kdesrc
end module
module raptor
repository git://github.com/dajobe/raptor.git
branch master
build-dir ~/kdesrc
override-build-system autotools
custom-build-command make
end module
#librdf will not compile properly under master or redland_1_0_16 - error about src/rdf_config.h.in not found.
#compiles fine under tag redland_1_0_15
module librdf
repository git://github.com/dajobe/librdf.git
#branch master
tag redland_1_0_15
build-dir ~/kdesrc
override-build-system autotools
configure-flags --with-mysql=yes
custom-build-command make
end module


Although, might I ask.. The git://github.com is not defined in the ~/.gitconfig, just in a sample, and it seems to be trusted like the ankngit.kde.org is. But when I try to create another module entry for:
module chakra-gtk-config
repository git://gitorious.org/chakra/chakra-gtk-config.git
branch master
build-dir ~/kdesrc
end module

using gitorious.org to pull an old release of the kde-gtk-config program without gtk3 support (to use on RHEL 6), I get the:
There is no repository assigned to git://gitorious.org/chakra/chakra-gtk-config.git when assigning a
module-set (kde-development) on line 323 of /home/ntruhan/.kdesrc-buildrc.
These repositories are defined by git-repository-base in the global

I tried to setup an alias for it with git-repository-base but then it went and tried to pull the project.kde.org database and then it there was an unknown module.

I tried various combinations of git-repository-base chakra git://gitorious.org/chakra with different parts of the url. I even changed it to a module-set and use-module for the .git module with the same result.

Thank you again! for your help and ALL the work you put into this great build system.

When trying to build a module such as kde-gtk-config, a section of configuration such as the following should do the trick:

Code: Select all

module quassel
    repository git://git.quassel-irc.org/quassel.git
    cmake-options -DWITH_KDE=TRUE
end module

Simply change the repository argument to point to the gitorious.org repository.