[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Problem compiling kdebindings - CVS HEAD/Fedora Core/Unsermake
From:       Richard Dale <Richard_Dale () tipitina ! demon ! co ! uk>
Date:       2004-04-28 8:53:42
Message-ID: 200404280953.42730.Richard_Dale () tipitina ! demon ! co ! uk
[Download RAW message or body]

On Wednesday 28 April 2004 09:07, Steven P. Ulrick wrote:
> The problem that I see is just that I can't seem to use Unsermake to
> compile this module.  But, if there is anything I can do to help with
> Unsermake, let me know :) I really like the idea behind Unsermake,
> therefore, is there a way to compile a module that Unsermake won't
> compile without having the comment out the line in my ".bash_profile"
> file that enables Unsermake?
I'm afraid I don't know anything about Unsermake. The kdebindings module 
doesn't compile with builddir != sourcedir, is that part of the problem? 

Not all the kdebindings in HEAD will build, the java bindings haven't been 
regenerated since the KDE 3.2.0 release for instance. They don't follow the 
kdelibs headers in 'real time', they are only sychronised for a major kde 
release.

On the other hand a lot of work has been done on kjsembed or qtruby/korundum 
since the initial release, and they will build fine in the HEAD branch. I 
think rather than just try and build everything, it's best to only build the 
project that you actually want to use for development. For java, use the 
KDE_3_2_BRANCH with the KDE 3.2.x release kdelibs. On the other hand for ruby 
or kjsembed, the HEAD branch is fine if you want the latest in 
fixes/enhancements.

-- Richard
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]