[PyQt] Importing marble fails

[heathmatlock]

I removed marble.so and libmarblewidget.so from
/usr/lib/python2.7/dist-packages/PyKDE4/ then configured and compiled
marble without specifying an install directory and installed as a root
user to system defaults. This time marble wasn't even found as
something to import, so I did updatedb && locate marble.so and I found
this:

/usr/local/lib/python2.7/site-packages/PyKDE4/marble.so

I then did this:
http://paste.kde.org/194852/

And as you can see it wasn't finding the marble module. I'm guessing
that maybe it still has something to do with paths.

On Sat, Jan 28, 2012 at 10:53 AM, heathmatlock <heathmatlock at gmail.com> wrote:
> On Sat, Jan 28, 2012 at 9:47 AM, David Boddie <david at boddie.org.uk> wrote:
>> On Sat, 28 Jan 2012 02:12:19 -0600, heathmatlock wrote:
>>
>>> I compiled one of the newer marble commits,
>>> 10c910a9cae3c4e8eb9be442d80125b7e7338e67, and copied the marble.so
>>> into  /usr/lib/python2.7/dist-packages/PyKDE4 and when I go to import
>>> marble within a python interpreter, this error is
>>> given:http://paste.kde.org/194432/
>>
>> Are you sure that the module.so file contains the Python bindings for Marble?
>> If you try to import a regular C/C++ library into Python, you will get the
>> same error.
>>
>> How did you configure the Marble build?
>
> I'm not sure that the file contains the Python bindings, it was just
> the best guess. This is what was used to configure marble:
> ~/Devel/build/marble$ cmake ../../src/marble/
> -DEXPERIMENTAL_PYTHON_BINDINGS=TRUE -DCMAKE_BUILD_TYPE=debugfull
> -DCMAKE_INSTALL_PREFIX=/home/heath/Devel/install/marble/
>
>
>
> --
> Heath Matlock
> +1 256 274 4225



-- 
Heath Matlock
+1 256 274 4225