Re: [Kde-bindings] Questions About the New Schedule

2007-10-03 Thread Dirk Mueller
On Monday, 1. October 2007, Richard Dale wrote:

> Well it all built for me until Dirk changed the smoke/kde/qtguess.pl.cmake
> file.

I synced it with the Qt version, which had critical bugfixes being applied by 
Caleb Tennis a few weeks ago to make it compile at all with Qt 4.3.0. I don't 
believe that anyone was able to compile kdebindings since then because 
qtguess was doing the wrong thing due to a new #define in qtconfig.h all the 
time. 

> I think the problem is that the FindQt4 cmake file used by the 
> smoke/qt build sets up a macro called QT_LIBRARIES, but the version of
> FindQt4 in KDE doesn't set that up.

both use the same FindQt4 macro, so this can't be the problem. 

> So we do need different 
> qtguess.pl.cmake files for smoke/qt, and for smoke/kde (and smoke/plasma).

huh?

> need to be pretty much complete, and we should only need to test for which
> we are on a Mac, Windows or Linux type build env for the window styles QT_
> defines.

and exactly that was removed because the qt guess script cannot figure that 
out due to it undefining QT_LICENSE_KEY and therefore breaking the build for 
all the tests it runs. 

I really wonder what kind of setup you use because I don't know anyone who was 
ever able to use the smoke bindings. if I ever find somebody then I'd love to 
figure out 


Greetings,
Dirk
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: [Kde-bindings] Questions About the New Schedule

2007-10-02 Thread Richard Dale
On Tuesday 02 October 2007, Richard Dale wrote:

> I use cmake to build the smoke libs and the ruby and python bindings, and
> it all works fine. I'm afraid I can't reproduce the perl error that the
> dashboard build has.
Oops, I meant Ruby and C# of course.

-- Richard
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: [Kde-bindings] Questions About the New Schedule

2007-10-02 Thread Richard Dale
On Monday 01 October 2007, Simon Edwards wrote:
> Hello all,
>
> Sebastian Kügler wrote:
> > On Monday 01 October 2007 10:37:06 Andreas Pakulat wrote:
> >> On 01.10.07 06:30:25, Dirk Mueller wrote:
> >>> On Saturday, 8. September 2007, Albert Astals Cid wrote:
> > 5)  Should language bindings be part of the development platform?
> > Richard Dale says "Python and Ruby in good shape by late October, and
> > possibly C# too."
> 
>  If Richard says he can do it, i say we can try it :-)
> >>>
> >>> Thats not enough. somebody has at least to be able to confirm that the
> >>> bindings *compile*. right now, kdebindings does not compile, and after
> >>> I spent an hour or so looking, I'm sure that it can not compile for
> >>> anyone at all, given the fundamental bugs in the build system.
> >>>
> >>> it is my understanding that Richard uses a completely different build
> >>> system to maintain the bindings, at least thats what he used to do in
> >>> KDE3 times. There has to be at least somebody who maintains the
> >>> official build system, and that person has to be != me.
I use cmake to build the smoke libs and the ruby and python bindings, and it 
all works fine. I'm afraid I can't reproduce the perl error that the 
dashboard build has. 

http://ktown.kde.org/~dirk/dashboard/

I just did a diff from the kalyptus code as it was in 2004, and how it is 
today and the line with the error is much the same:

@@ -226,17 +217,18 @@
 # Otherwise, compile the default ones. Used for filtering in readCxxLine.
 if ( my @qt_defines = map { ($_=~m/^QT_(.*)/)[0] } keys %defines)
 {
-my $regexp = "m/^#\\s*ifn?def\\s+QT_(?:" . join('|', map 
{ "\$qt_defines[$_]" } 0..$#qt_defines).")/o";
+my $regexp = "m/^#\\s*if\\s*[n!]?\\s*def(ined\\()?\\s*QT_(?:" . join('|', 
map { "\$qt_defines[$_]" } 0..$#qt_defines).")/o";
 $match_qt_defines = eval "sub { my \$s=shift;
-   \$s=~/^#\\s*if(n)?def/ || return 0;
+   \$s=~/^#\\s*if\\s*([n!])?\s*def(ined\\()?
\\s*QT_/ || return 0;
if(!\$1) { return \$s=~$regexp ? 0:1 }
else { return \$s=~$regexp ? 1:0 }
   }";
+
 die if $@;

I couldn't understand the perl in 2004, and I don't really understand it now. 
Certainly lots of people have run kalyptus to build the smoke bindings, and 
only dashboard has this error:

Global symbol "$qt_defines" requires explicit package name at (eval 1) line 4.
Global symbol "$qt_defines" requires explicit package name at (eval 1) line 4.
Global symbol "$qt_defines" requires explicit package name at (eval 1) line 4.
...propagated at kdebindings-717467/kalyptus/kalyptus line 227.
make: *** [smoke/plasma/smokedata.cpp] Error 255
make: *** [smoke/plasma/CMakeFiles/smokeplasma.dir/all] Error 2
make: *** [all Error 2

This is the code that is failing:

# Check the %defines hash for QT_* symbols and compile the corresponding RE
# Otherwise, compile the default ones. Used for filtering in readCxxLine.
if ( my @qt_defines = map { ($_=~m/^QT_(.*)/)[0] } keys %defines)
{
my $regexp = "m/^#\\s*if\\s*[n!]?\\s*def(ined\\()?\\s*QT_(?:" . join('|', 
map { "\$qt_defines[$_]" } 0..$#qt_defines).")/o";
$match_qt_defines = eval "sub { my \$s=shift;
   \$s=~/^#\\s*if\\s*([n!])?\s*def(ined\\()?
\\s*QT_/ || return 0;
   if(!\$1) { return \$s=~$regexp ? 0:1 }
   else { return \$s=~$regexp ? 1:0 }
  }";

die if $@;
}

Would it help to move the 'my @qt_defines' outside the 'if' statement? Without 
being able to reproduce the bug, this is impossible to fix for me.

my @qt_defines;

if (@qt_defines = map { ($_=~m/^QT_(.*)/)[0] } keys %defines)
{

-- Richard
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: [Kde-bindings] Questions About the New Schedule

2007-10-01 Thread Richard Dale
On Monday 01 October 2007, Pau Garcia i Quiles wrote:
> > I think the problem is that the FindQt4 cmake file used by the smoke/qt
> > build sets up a macro called QT_LIBRARIES, but the version of FindQt4 in
> > KDE doesn't set that up. So we do need different qtguess.pl.cmake files
> > for smoke/qt, and for smoke/kde (and smoke/plasma).
>
> ^^^ Wouldn't it be easier to have a single FindQt4 cmake file instead  
> of the *eight* different ones we have now?  
> (http://lists.kde.org/?l=kde-core-devel&m=119116801902968&w=2)
What a nightmare!

-- Richard

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: [Kde-bindings] Questions About the New Schedule

2007-10-01 Thread Pau Garcia i Quiles
Quoting Richard Dale <[EMAIL PROTECTED]>:

> On Monday 01 October 2007, Dirk Mueller wrote:
>> On Monday, 1. October 2007, Cyrille Berger wrote:
>> > > According to that, it has not build in almost 2 and a half months.
>> >
>> > Hum right I have disabled plasma, maybe it should be disabled by default.
>> > CCing kde-bindings.
>>
>> I have it disabled as well. in fact I only try to build the smoke-qt
>> bindings. but the qtguess configury (whatever it is good for) runs twice,
>> and 2nd time it fails completely, aborting the build.
>>
>> I've mailed the log already to Richard Dale and I already disabled the
>> smoke-kde bindings (which couldn't be build at all due to a desynchronized
>> copy of qtguess.pl.in), but no result so far.
> Well it all built for me until Dirk changed the smoke/kde/qtguess.pl.cmake
> file.

> I think the problem is that the FindQt4 cmake file used by the smoke/qt
> build sets up a macro called QT_LIBRARIES, but the version of FindQt4 in KDE
> doesn't set that up. So we do need different qtguess.pl.cmake files for
> smoke/qt, and for smoke/kde (and smoke/plasma).

^^^ Wouldn't it be easier to have a single FindQt4 cmake file instead  
of the *eight* different ones we have now?  
(http://lists.kde.org/?l=kde-core-devel&m=119116801902968&w=2)

>
> I find these perl scripts largely unmaintainable and they should all be
> removed and cmake-only tests used. The Qt build options for building KDE need
> to be pretty much complete, and we should only need to test for which we are
> on a Mac, Windows or Linux type build env for the window styles QT_ defines.
>
> -- Richard
> ___
> Kde-bindings mailing list
> [EMAIL PROTECTED]
> https://mail.kde.org/mailman/listinfo/kde-bindings
>



-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: [Kde-bindings] Questions About the New Schedule

2007-10-01 Thread Richard Dale
On Monday 01 October 2007, Dirk Mueller wrote:
> On Monday, 1. October 2007, Cyrille Berger wrote:
> > > According to that, it has not build in almost 2 and a half months.
> >
> > Hum right I have disabled plasma, maybe it should be disabled by default.
> > CCing kde-bindings.
>
> I have it disabled as well. in fact I only try to build the smoke-qt
> bindings. but the qtguess configury (whatever it is good for) runs twice,
> and 2nd time it fails completely, aborting the build.
>
> I've mailed the log already to Richard Dale and I already disabled the
> smoke-kde bindings (which couldn't be build at all due to a desynchronized
> copy of qtguess.pl.in), but no result so far.
Well it all built for me until Dirk changed the smoke/kde/qtguess.pl.cmake 
file. I think the problem is that the FindQt4 cmake file used by the smoke/qt 
build sets up a macro called QT_LIBRARIES, but the version of FindQt4 in KDE 
doesn't set that up. So we do need different qtguess.pl.cmake files for 
smoke/qt, and for smoke/kde (and smoke/plasma).

I find these perl scripts largely unmaintainable and they should all be 
removed and cmake-only tests used. The Qt build options for building KDE need 
to be pretty much complete, and we should only need to test for which we are 
on a Mac, Windows or Linux type build env for the window styles QT_ defines.

-- Richard
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team