In consequence USE="kig-scripting" has no effect - scripting is never eactivated. The problem is, that they hardcode some boost_python-libnames in their FindBoostPython.cmake-file, none of them matching one installed by Gentoo: set(PYTHON_LIBS "boost_python-gcc-mt;boost_python-mt;boost_python-gcc-mt-1_33;boost_python-gcc-mt-1_33_1;boost_python;boost_python-gcc-mt-1_32;boost_python") A sed like sed -ie 's/\(set(PYTHON_LIBS \)"\(.*\)"/\1"boost_python-2.7-1_49"/' cmake/FindBoostPython.cmake fixes the issue, of course using gentoo-tools instead of hardcoding another name ;) (I don't know how to do this, as there is no boost.eclass - eselect probably?" I am sure kig <4.9.0 is affected, too.
Made a patch applied to kde-base/kig-4.9.49.9999 and kde-base/kig-9999. Please test and review
Created attachment 322633 [details] Modified patch to enable optional scripting features The patch from the overlay made kig compile and build files from scripting-subdir. When following http://docs.kde.org/stable/en/kdeedu/kig/scripting.html the mentioned action in the menu was not present. That was because the "KIG_ENABLE_PYTHON_SCRIPTING" was not set. The modified patch sets it and now the option is available and the example script works.
(In reply to comment #2) > Created attachment 322633 [details] > Modified patch to enable optional scripting features > > The patch from the overlay made kig compile and build files from > scripting-subdir. > When following > http://docs.kde.org/stable/en/kdeedu/kig/scripting.html > the mentioned action in the menu was not present. That was because the > "KIG_ENABLE_PYTHON_SCRIPTING" was not set. The modified patch sets it and > now the option is available and the example script works. Thanks for testing, updated the patch according your changes.
Thanks all. KDE SC 4.9.1 is now in tree. Sync in some hours to get the change. + 04 Sep 2012; Johannes Huber <johu@gentoo.org> + +files/kig-4.9.0-boostpython.patch, +kig-4.9.1.ebuild, metadata.xml: + Version bump KDE SC 4.9.1
