Mas OS X compiler errors

Help
gelo
2010-02-10
2013-05-08
  • gelo

    gelo - 2010-02-10

    Hi,

    I am trying to install tuxcap 1.4.0 on Snow Leopard, but i have problems with compiler errors. I have installed MacPorts and used it to install ImageMagick 6.5.9-0 and all related packages. I run "cmake" and get this:

    mac02:tuxcap-build tester$ cmake ../tuxcap
    - 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
    - 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
    - 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
    CMake Error at CMakeLists.txt:2 (INCLUDE):
      include could not find load file:

        /tuxcap/CMakeMacros/IJMacros.txt

    • Found ImageMagick: TRUE
    • Found PythonLibs: -framework Python
      CMake Warning at CMakeLists.txt:22 (FIND_PACKAGE):
        Could not find module FindImageMagickLib.cmake or a configuration file for
        package ImageMagickLib.

      Adjust CMAKE_MODULE_PATH to find FindImageMagickLib.cmake or set
      ImageMagickLib_DIR to the directory containing a CMake configuration file
      for ImageMagickLib.  The file will have one of the following names:

        ImageMagickLibConfig.cmake
        imagemagicklib-config.cmake

    CMake Warning at CMakeLists.txt:24 (FIND_PACKAGE):
      Could not find module FindAudiereLib.cmake or a configuration file for
      package AudiereLib.

      Adjust CMAKE_MODULE_PATH to find FindAudiereLib.cmake or set AudiereLib_DIR
      to the directory containing a CMake configuration file for AudiereLib.  The
      file will have one of the following names:

        AudiereLibConfig.cmake
        audierelib-config.cmake

    Python development libraries found, building TuxCap Python bindings and examples
    Python libraries -framework Python include path /System/Library/Frameworks/Python.framework/Headers
    libSDL found. /Library/Frameworks/SDL.framework/Headers /Library/Frameworks/SDL.framework;-framework Cocoa
    CMake Error at CMakeLists.txt:82 (MESSAGE):
      lib ImageMagick requested but not found.

    CMake Warning (dev) in CMakeLists.txt:
      No cmake_minimum_required command is present.  A line of code such as

        cmake_minimum_required(VERSION 2.8)

      should be added at the top of the file.  The version specified may be lower
      if you wish to support older CMake versions for this project.  For more
      information run "cmake -help-policy CMP0000".
    This warning is for project developers.  Use -Wno-dev to suppress it.

    • Configuring incomplete, errors occurred!
     
  • W.P. van Paassen

    Hi,

    I looks like you're running cmake from the wrong directory, go into the build directory and issue a cmake ..

    Cheers

     
  • gelo

    gelo - 2010-02-11

    Hi, thank you for your answer !

    I'm new to Mac OS and don't have much experience. I do next steps to compile tuxcap:

    I have uncompressed "libtuxcap-1.4.0" directory in Mac OS "/" directory ("/libtuxcap-1.4.0"). So, I run a console application and type this:

    mac02:~ tester$ cd /
    mac02:/ tester$ cd libtuxcap-1.4.0
    mac02:libtuxcap-1.4.0 tester$ cd tuxcap-build

    i suppose i'm in "/libtuxcap-1.4.0/tuxcap-build" directory now, so i type "cmake ../tuxcap" and it writes me the same things as in post №1:

    Last login: Thu Feb 11 11:02:53 on ttys000
    mac02:~ tester$ cd /
    mac02:/ tester$ cd libtuxcap-1.4.0
    mac02:libtuxcap-1.4.0 tester$ cd tuxcap-build
    mac02:tuxcap-build tester$ cmake ../tuxcap
    - 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
    - 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
    - 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
    CMake Error at CMakeLists.txt:2 (INCLUDE):
      include could not find load file:

        /tuxcap/CMakeMacros/IJMacros.txt

    • Found ImageMagick: TRUE
    • Found PythonLibs: -framework Python
      CMake Warning at CMakeLists.txt:22 (FIND_PACKAGE):
        Could not find module FindImageMagickLib.cmake or a configuration file for
        package ImageMagickLib.

      Adjust CMAKE_MODULE_PATH to find FindImageMagickLib.cmake or set
      ImageMagickLib_DIR to the directory containing a CMake configuration file
      for ImageMagickLib.  The file will have one of the following names:

        ImageMagickLibConfig.cmake
        imagemagicklib-config.cmake

    CMake Warning at CMakeLists.txt:24 (FIND_PACKAGE):
      Could not find module FindAudiereLib.cmake or a configuration file for
      package AudiereLib.

      Adjust CMAKE_MODULE_PATH to find FindAudiereLib.cmake or set AudiereLib_DIR
      to the directory containing a CMake configuration file for AudiereLib.  The
      file will have one of the following names:

        AudiereLibConfig.cmake
        audierelib-config.cmake

    Python development libraries found, building TuxCap Python bindings and examples
    Python libraries -framework Python include path /System/Library/Frameworks/Python.framework/Headers
    libSDL found. /Library/Frameworks/SDL.framework/Headers /Library/Frameworks/SDL.framework;-framework Cocoa
    CMake Error at CMakeLists.txt:82 (MESSAGE):
      lib ImageMagick requested but not found.

    CMake Warning (dev) in CMakeLists.txt:
      No cmake_minimum_required command is present.  A line of code such as

        cmake_minimum_required(VERSION 2.8)

      should be added at the top of the file.  The version specified may be lower
      if you wish to support older CMake versions for this project.  For more
      information run "cmake -help-policy CMP0000".
    This warning is for project developers.  Use -Wno-dev to suppress it.

    • Configuring incomplete, errors occurred!
      mac02:tuxcap-build tester$
     
  • W.P. van Paassen

    Hi,

    Don't do a cmake ../tuxcap, do a cmake ..
    (that's cmake with two points to indicate the directory higher in the tree)

    cheers

     
  • gelo

    gelo - 2010-02-11

    Hi! Thanks for your post! It fixed some errors, but still i've got problems:

    Last login: Thu Feb 11 13:50:31 on ttys000
    mac02:~ tester$ cd /
    mac02:/ tester$ cd libtuxcap-1.4.0
    mac02:libtuxcap-1.4.0 tester$ cd tuxcap-build
    mac02:tuxcap-build tester$ cmake ..
    - 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
    - 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
    - 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
    - Found ImageMagick: TRUE
    - Found PythonLibs: -framework Python
    CMake Error at tuxcap/CMakeModules/FindImageMagickLib.cmake:127 (MESSAGE):
      FindImageMagick could not find ImageMagick++ library or header(s)
    Call Stack (most recent call first):
      tuxcap/CMakeLists.txt:22 (FIND_PACKAGE)

    Python development libraries found, building TuxCap Python bindings and examples
    Python libraries -framework Python include path /System/Library/Frameworks/Python.framework/Headers
    libSDL found. /Library/Frameworks/SDL.framework/Headers /Library/Frameworks/SDL.framework;-framework Cocoa
    CMake Error at tuxcap/CMakeLists.txt:82 (MESSAGE):
      lib ImageMagick requested but not found.

    • Configuring incomplete, errors occurred!
      mac02:tuxcap-build tester$
     
  • W.P. van Paassen

    Did you install Magick++? These are the c++ bindings to libImageMagick. Maybe macports did not install these?

     
  • gelo

    gelo - 2010-02-11

    Yes, i did. I had been installed ImageMagick and a lot of dependencies through MacPorts before i tried to compile tuxcap. Is it possible to install libImageMagick separately?

     
  • W.P. van Paassen

    Try to find out where your Magick++ is installed, then
    take a look at tuxcap/CMakeModules/FindImageMagickLib.cmake and try to see why it can't find it.
    It might be the case that with newer versions of cmake this script (tuxcap/CMakeModules/FindImageMagickLib.cmake) is not necessary anymore and that cmake has its own/better version, so you can try to remove it and see what happens

     
  • gelo

    gelo - 2010-02-11

    Thanks a lot ! Now i've got libtuxcap.a and libtuxcap.4.0.dylib !

    My copy of MacPorts 1.8.2 is located in "/opt" directory. ImageMagick headers and libs are located in "/opt/local/include/ImageMagick" and "/opt/local/lib" appropriately. I added two lines at the bottom of each block in "tuxcap/CMakeModules/FindImageMagickLib.cmake" like this:

    # find the libraries main include header file
    FIND_PATH(IMAGEMAGICKLIB_INCLUDE_DIR Magick++.h
      "${IMAGEMAGICKLIB_DIR}/include"
      "$ENV{IMAGEMAGICKLIB_DIR}/include"
      "$ENV{MAGICK_DIR}/include"
      "${IMAGEMAGICKLIB_HOME}/include"
      "$ENV{IMAGEMAGICKLIB_HOME}/include"
      "$ENV{MAGICK_HOME}/include"
      "/include"
      /usr/local/include
      /usr/include
      /usr/include/ImageMagick
      /opt/net/gcc41/ImageMagick/include
      /opt/net/gcc33/ImageMagick/include
      /opt/local/include/ImageMagick
      )
    #MESSAGE("DBG IMAGEMAGICKLIB_INCLUDE_DIR=${IMAGEMAGICKLIB_INCLUDE_DIR}")

    # set directories to search for libraries:
    SET(IMAGEMAGICKLIB_POSSIBLE_LIBRARY_PATHS
      "${IMAGEMAGICKLIB_DIR}/lib"
      "$ENV{IMAGEMAGICKLIB_DIR}/lib"
      "$ENV{MAGICK_DIR}/lib"
      "${IMAGEMAGICKLIB_HOME}/lib"
      "$ENV{IMAGEMAGICKLIB_HOME}/lib"
      "$ENV{MAGICK_HOME}/lib"
      "/lib"
      ""
      "/lib" 
      /usr/local/lib
      /usr/lib
      /opt/net/gcc41/ImageMagick/lib 
      /opt/net/gcc33/ImageMagick/lib
      /opt/local/lib 
      )
    #MESSAGE("DBG IMAGEMAGICKLIB_POSSIBLE_LIBRARY_PATHS=${IMAGEMAGICKLIB_POSSIBLE_LIBRARY_PATHS}")

    also i changes "#include <linux/types.h>" to "#include <sys/types.h> in "Physics.h" file.

     
  • W.P. van Paassen

    Nice!

    Now try to run hungarr or some of the demo's.

    btw I think there's still a problem with 3D enabled on Mac. Take a look in the D3DInterface.cpp file, look in the Init function for the
    while true loop. This won't work on mac. Exchange it for
     
    GLint max_texture_size;
    glGetIntegerv(GL_MAX_TEXTURE_SIZE, &max_texture_size);

    #if 0
      //  while (true) {
      //glTexImage2D(GL_PROXY_TEXTURE_2D, 0, GL_RGBA,  try_width << 1, try_height << 1, 0, GL_RGBA, GL_UNSIGNED_BYTE, NULL); 
        GLint width = 0;
        glGetTexLevelParameteriv(GL_PROXY_TEXTURE_2D, 0, GL_MAX_TEXTURE_SIZE, &width);
        GLint height = 0;
        glGetTexLevelParameteriv(GL_PROXY_TEXTURE_2D, 0, GL_TEXTURE_HEIGHT, &height);
       
        if (width != 0)
          try_width <<= 1;
       
        if (height != 0)
          try_height <<= 1;

        if (width == 0 && height == 0)
          break;
      }
    #endif

    Cheers

     
  • gelo

    gelo - 2010-02-11

    Thanks! I take it into account.

    Some of apps crash on execution. demo_1 and all of physics demos work fine. i think they don't use textures.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks