On 4/22/10, lux-integ <[email protected]> wrote: > I have already installed pyKDE4 from kdebindings-4.4.2. Does the above > mean that if the marble library is required I have to re-compile pyKDE4 > > with "-DEXPERIMENTAL_PYTHON_BINDINGS=TRUE" passed to cmake or is it > another > procedure and if so what is it?
I have these ones unpacked for examination purposes: find /sources/KDE/4.4.2 -maxdepth 1 -type d /sources/KDE/4.4.2 /sources/KDE/4.4.2/kdeedu-4.4.2 /sources/KDE/4.4.2/kdebindings-4.4.2 /sources/KDE/4.4.2/kdebase-workspace-4.4.2 /sources/KDE/4.4.2/kdebase-runtime-4.4.2 /sources/KDE/4.4.2/kdebase-4.4.2 /sources/KDE/4.4.2/kdeutils-4.4.2 /sources/KDE/4.4.2/kdelibs-4.4.2 /sources/KDE/4.4.2/kdemultimedia-4.4.2 The only one showing EXPERIMENTAL_PYTHON_BINDINGS is kdeedu l...@lfs:/sources/KDE/4.4.2$ grep -I -r EXPERIMENTAL_PYTHON_BINDINGS . ./kdeedu-4.4.2/marble/docs/bindings/python/Python_bindings_for_marble_library.txt:The bindings are not built by default. To build them pass the option -DEXPERIMENTAL_PYTHON_BINDINGS=TRUE to cmake and make sure that the Python support from the kde-bindings module is installed. ./kdeedu-4.4.2/CMakeLists.txt:macro_log_feature(EXPERIMENTAL_PYTHON_BINDINGS "Experimental Python binding support for the Marble library" "Experimental Python binding support for the Marble library" ./kdeedu-4.4.2/CMakeLists.txt: "Experimental Python binding support for the Marble library. To activate it pass -DEXPERIMENTAL_PYTHON_BINDINGS=TRUE to cmake.") ./kdeedu-4.4.2/CMakeLists.txt:if(EXPERIMENTAL_PYTHON_BINDINGS) ./kdeedu-4.4.2/CMakeLists.txt:endif(EXPERIMENTAL_PYTHON_BINDINGS) That flag is therefore apparently meant for building kdeedu -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
