compile.sh build failed on OSX

[Wolf St. Kappesser]

Got this error on Mac OS X 10.6.6 with widelands revno: 5842 [merge] after

# sh ./compile.sh :

Should Widelands be build in [r]elease or [d]ebug mode?

r

  -> Release mode selected

-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Checking whether C compiler has -isysroot
-- Checking whether C compiler has -isysroot - yes
-- Checking whether C compiler supports OSX deployment target flag
-- Checking whether C compiler supports OSX deployment target flag - yes
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Checking whether CXX compiler has -isysroot
-- Checking whether CXX compiler has -isysroot - yes
-- Checking whether CXX compiler supports OSX deployment target flag
-- Checking whether CXX compiler supports OSX deployment target flag - yes
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Disabled Unit Tests
-- Boost version: 1.45.0
-- Using compiler flags: -O2 -DNDEBUG
CMake Error at cmake/Modules/FindGGZ_Core.cmake:18 (MESSAGE):
  Could not find GGZ_Core
Call Stack (most recent call first):
  CMakeLists.txt:259 (find_package)

-- Configuring incomplete, errors occurred!

EDIT:
The problem: I have my libs and includes installed in a non standard folder. Which way I should use to inform compile.sh about this paths?

[Nicolai Hähnle (nha)]

The error message indicates very clearly that this is because the GGZ libraries are either not installed or cannot be found. Please install those libraries and try again.

[Nicolai Hähnle (nha)]

On second thought, Jens, do you think it would be possible to display an informative text message that indicates to the user where those libraries can be downloaded from? I remember seeing such messages in the KDE build process, and they are of course very useful to prevent this type of bug reports.

[Nicolai Hähnle (nha)]

I suppose it depends on how non-standard that path is. Can you give more information, please?

compile.sh can only find automatically what cmake can find automatically, and if the installation path is sufficiently non-standard, then it's your responsibility to tell cmake about that, by invoking it directly instead of via the convenience script. Refer to doc/README.compiling for general info on how you would do that - I see it's lacking Mac OS X specific information, but it should be similar to under Linux.

If somebody with a Mac runs across this report, do you think you could extend that README accordingly?

[Wolf St. Kappesser (wsk)]

I think it will work with 'export'. I will try to update the compiling instructions on webpage and the readme for osx.

[Wolf St. Kappesser (wsk)]

I have edit the build instructions on the website. You can adapt the README simply by use this page infos. Think the issue is solved. Greets WSK