chrisburel / perlqt4

Automatically exported from code.google.com/p/perlqt4
Other
0 stars 0 forks source link

What is the official git repository for perlqt4 ??????? #59

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Is it here?:
git clone https://code.google.com/p/perlqt4/

Or is it there?:
git clone git://anongit.kde.org/perlqt/

Looking at QtCore4.pm, the more bugfixed version is the second one. Right.

If I need to submit patches, what is the reference?

Thanks for fixing that.

Original issue reported on code.google.com by olivier....@gmail.com on 5 Jul 2014 at 8:31

GoogleCodeExporter commented 9 years ago
The one hosted on KDE is just the PerlQt code.  Because the KDE git repos are 
modular, you'd have to download, build, and install smokegen, smokeqt, and 
perlqt as 3 separate steps.  These are built with CMake.
The one hosted on Google Code is the "standalone" release.  It exists mainly to 
supply a Makefile.PL, and to make building smokegen, smokeqt, and perlqt in one 
step.

It was intended that the code be kept in sync.  However, it is possible that 
some drift has happened. A standalone release hasn't been made in a few years.

The KDE repo is the canonical one.

Original comment by chrisbu...@gmail.com on 5 Jul 2014 at 10:16

GoogleCodeExporter commented 9 years ago
They are not in sync anymore. At least, this diff to support perl-5.18.0 is in 
kde repo.
https://projects.kde.org/projects/kde/kdebindings/perl/perlqt/repository/revisio
ns/aa2083b40c83fad6b931a2088ae69bc206a7edc7

Particulary, this part of the patch is important:
https://projects.kde.org/projects/kde/kdebindings/perl/perlqt/repository/revisio
ns/aa2083b40c83fad6b931a2088ae69bc206a7edc7/diff/qtcore/lib/QtCore4.pm

It fixes #58 (AUTOLOAD redefinition) and also fixes #57

Please sync repos. I'm currently writing a big patch for #44 and #46.

Original comment by olivier....@gmail.com on 6 Jul 2014 at 6:28

GoogleCodeExporter commented 9 years ago
I've pulled in the changes from the kde repo.  Can you check these changes and 
see if they're working for you?

Original comment by chrisbu...@gmail.com on 6 Jul 2014 at 2:45

GoogleCodeExporter commented 9 years ago
It build fine, thanks.
I've attached the log thaty shows that only one test 
fails:perlqt_widgetswiggly.(#10)

Ignore the last error, it's the rpmbuild log that fails due to failed test. If 
I disable %check, it builds fine.

Aside that, I've noticed 3 warnings:

/home/ol222822/rpmbuild/BUILD/Qt-0.96.0/qtdbus/tools/qdbusxml2perl/qdbusxml2perl
.cpp: In function 'void writeAdaptor(const QString&, const Interfaces&)':
/home/ol222822/rpmbuild/BUILD/Qt-0.96.0/qtdbus/tools/qdbusxml2perl/qdbusxml2perl
.cpp:946:22: warning: variable 'usingInvokeMethod' set but not used 
[-Wunused-but-set-variable]
                 bool usingInvokeMethod = false;
                      ^
/home/ol222822/rpmbuild/BUILD/Qt-0.96.0/qtdbus/tools/qdbusxml2perl/qdbusxml2perl
.cpp: At global scope:
/home/ol222822/rpmbuild/BUILD/Qt-0.96.0/qtdbus/tools/qdbusxml2perl/qdbusxml2perl
.cpp:274:16: warning: 'QString cpp(const QString&)' defined but not used 
[-Wunused-function]
 static QString cpp(const QString &name)
                ^
/home/ol222822/rpmbuild/BUILD/Qt-0.96.0/qtcore/src/util.cpp:2254:59: warning: 
converting 'false' to pointer type 'void*' [-Wconversion-null]
         static smokeperl_object nothis = { 0, 0, 0, false };

Original comment by olivier....@gmail.com on 7 Jul 2014 at 8:30

Attachments:

GoogleCodeExporter commented 9 years ago
Bad news, on centos6 and centos7 beta it doesn't build anymore :-(
It fails to detect SMOKE_QWT_LIBRARY (see attached log)

(The successfull build was done on fc-20)

Original comment by olivier....@gmail.com on 7 Jul 2014 at 9:35

Attachments:

GoogleCodeExporter commented 9 years ago
Note: on rhel6, which ships cmake-2.6.4, I have the following error as well:
Make Error at CMakeLists.txt:91 (string):
  string end index: -1 is out of range 0 - 17

This error doesn't appear on centos7 beta (cmake-2.8.11) or fedora core 20 
(cmake-2.8.12).

Original comment by olivier....@gmail.com on 7 Jul 2014 at 1:08

GoogleCodeExporter commented 9 years ago
The above error is fixed by patch provided in ticket #62.

You can close.

Original comment by olivier....@gmail.com on 11 Jul 2014 at 9:57

GoogleCodeExporter commented 9 years ago

Original comment by chrisbu...@gmail.com on 13 Jul 2014 at 4:21