search

chrisburel / perlqt4

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

example code doesn't run #24

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. build PerlQt4 following instructions from the README
2. cd into examples dir
3. run any example code

What is the expected output? 

A GUI

What do you see instead?

Can't load '/usr/local/lib/perl/5.10.0/auto/Qt4/Qt4.so' for module Qt4: 
libsmokeqt.so.2: cannot open shared object file: No such file or directory 
at /usr/lib/perl/5.10/XSLoader.pm line 64. 
at /usr/local/lib/perl/5.10.0/Qt4.pm line 1453

What version of the product are you using? 

I pulled the code from svn, version 461 

On what operating system?

Debian Lenny

Please provide any additional information below.

I like cookies.

Original issue reported on code.google.com by jeremiah...@gmail.com on 5 Dec 2009 at 10:25

GoogleCodeExporter commented 9 years ago 
1. Make sure libsmokeqt.so.2 got installed.  By default it would be in
/usr/local/lib/libsmokeqt.so.2.
2. Try running "sudo ldconfig /usr/local/lib".  That will refresh the linker's 
cache
of the system's shared libraries, including the newly installed libsmokeqt.so.2.

Original comment by chrisbu...@gmail.com on 7 Dec 2009 at 7:36

GoogleCodeExporter commented 9 years ago 
  1. Make sure libsmokeqt.so.2 got installed.  By default it would be in
  /usr/local/lib/libsmokeqt.so.2.

libsmokeqt.so.2 is installed in /usr/local/lib.

2. Try running "sudo ldconfig /usr/local/lib".  That will refresh the linker's 
cache
of the system's shared libraries, including the newly installed libsmokeqt.

Will I need to re-build after I do that using cmake, etc?

Original comment by jeremiah...@gmail.com on 8 Dec 2009 at 5:22

GoogleCodeExporter commented 9 years ago 
Will I need to re-build after I do that using cmake, etc?

No.  It is just a matter of getting the linker to see the new library.
One thing that should definitely work is to use the LD_LIBRARY_PATH environment
variable.  So, if you were running the mainwindows/mdi example, you could run
$> env LD_LIBRARY_PATH=/usr/local/lib perl examples/mainwindows/mdi/mdi.pl

But it stinks to have to set $LD_LIBRARY_PATH every time you want to run 
something
that uses PerlQt.  That's where the linker's library cache comes in.  Running
$> sudo ldconfig /usr/local/lib
should make it so you don't have to specify LD_LIBRARY_PATH, so that you can 
just run
it like so:
$> examples/mainwindows/mdi/mdi.pl

Hope that gets you up and running.

Original comment by chrisbu...@gmail.com on 8 Dec 2009 at 6:24

GoogleCodeExporter commented 9 years ago 
Since this isn't a problem with the bindings themselves, but with system
configuration, I'm closing this as Invalid.

Original comment by chrisbu...@gmail.com on 16 Dec 2009 at 6:38

GoogleCodeExporter commented 9 years ago 
I will follow up on this issue I just have been a little busy. :)

Original comment by jeremiah...@gmail.com on 17 Dec 2009 at 8:25