diff options
Diffstat (limited to 'kig/configure.in.bot')
| -rw-r--r-- | kig/configure.in.bot | 40 |
1 files changed, 40 insertions, 0 deletions
diff --git a/kig/configure.in.bot b/kig/configure.in.bot new file mode 100644 index 00000000..a1e0bbde --- /dev/null +++ b/kig/configure.in.bot @@ -0,0 +1,40 @@ +if test x$kig_warn_about_disabling_python = xyes; then + cat << EOF + +Kig Python scripting support has been disabled, because you +are missing the necessary headers and/or libraries. +In order to use Kig Python scripting, you need to have +Python installed, along with its development package ( e.g. +libpython-dev ), and also the Boost.Python library, along with +its development package ( e.g. libboost-python-dev ). + +Kig will continue to function without Python scripting support, +but you will not be able to created Python scripted objects, or +load Kig files that use them. + +Installing the libraries: +The python development libraries themselves are almost certainly +packaged by your favourite distribution. Look for a package name +like libpython-dev, with possibly a version number inserted +somewhere in the name.. For the Boost.Python libs, check this +documentation: "http://boost.org/more/download.html" and +"http://boost.org/more/download.html#Installation" or look for +a package like libboost-python-dev or libboost-dev.. +EOF +fi + +if test "x$kig_enable_python_scripting" = "xyes"; then + # tell users about the Boost.Python 1.30 + GCC 3.2+ problem and patch. + cat << EOF + +Kig WARNING +=========== +There is a problem using unpatched Boost.Python 1.30 in combination +with GCC 3.2 and above. In some distributions, like Debian sarge, +this problem has been fixed, but in other distributions, the problem +may still be there. If you encounter problems while compiling Kig, +then you should try to re-run configure with the option +"--disable-kig-python-scripting". This may fix the compilation, but +you will not be able to use the Kig Python Scripting. +EOF +fi |