Problems installing pymesh

[jsll]

Hi,

I followed your recommendation on how to install pymesh but to no success

workon pd_mesh_net pip install git+git://github.com/PyMesh/PyMesh.git@93d182c0a7cee446e89fac74033347d900054af4

This spits out a lot of errors (below you can see some)

    -- Could NOT find MKL (missing: MKL_LIBRARIES MKL_INCLUDE_DIRS MKL_INTERFACE_LIBRARY MKL_SEQUENTIAL_LAYER_LIBRARY MKL_CORE_LIBRARY)
    CMake Warning (dev) at cmake/FindAllDependencies.cmake:14 (FIND_PACKAGE):
      Policy CMP0074 is not set: find_package uses <PackageName>_ROOT variables.
      Run "cmake --help-policy CMP0074" for policy details.  Use the cmake_policy
      command to set the policy and suppress this warning.
    
      CMake variable TBB_ROOT is set to:
    
        /tmp/pip-req-build-vtbeqxh5/python/pymesh/third_party/
    
      For compatibility, CMake is ignoring the variable.
    Call Stack (most recent call first):
      Settings.cmake:24 (FIND_PACKAGE)
      CMakeLists.txt:5 (INCLUDE)
    This warning is for project developers.  Use -Wno-dev to suppress it.
    
    -- Could NOT find OpenCL (missing: OPENCL_LIBRARIES)
    -- SparseHash not found, consider set $SPARSEHASH_PATH environment variable (missing: SPARSEHASH_INCLUDE_DIRS)
    -- Found Boost: /usr/include (found version "1.65.1") found components: atomic chrono date_time system thread
    -- Using header-only CGAL
    -- Found Boost: /usr/include (found suitable version "1.65.1", minimum required is "1.48")
    -- Boost include dirs: /usr/include
    -- Boost libraries:
    -- Using gcc version 4 or later. Adding -frounding-math
    CMake Warning (dev) at /usr/local/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:272 (message):
      The package name passed to `find_package_handle_standard_args` (MMG) does
      not match the name of the calling package (Mmg).  This can lead to problems
      in calling code that expects `find_package` result variables (e.g.,
      `_FOUND`) to follow a certain pattern.
    Call Stack (most recent call first):
      cmake/FindMmg.cmake:61 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
      cmake/FindAllDependencies.cmake:57 (FIND_PACKAGE)
      Settings.cmake:24 (FIND_PACKAGE)
      CMakeLists.txt:5 (INCLUDE)
    This warning is for project developers.  Use -Wno-dev to suppress it.
    
    -- Quartet library cannot be found.  Consider set QUARTET_PATH environment variable (missing: QUARTET_INCLUDE_DIRS QUARTET_LIBRARIES)
    CMake Warning (dev) at /usr/local/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:272 (message):
      The package name passed to `find_package_handle_standard_args` (LIBIGL)
      does not match the name of the calling package (libigl).  This can lead to
      problems in calling code that expects `find_package` result variables
      (e.g., `_FOUND`) to follow a certain pattern.
    Call Stack (most recent call first):
      cmake/Findlibigl.cmake:18 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
      cmake/FindAllDependencies.cmake:96 (FIND_PACKAGE)
      Settings.cmake:24 (FIND_PACKAGE)
      CMakeLists.txt:5 (INCLUDE)
    This warning is for project developers.  Use -Wno-dev to suppress it.
    
    CMake Warning (dev) at /usr/local/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:272 (message):
      The package name passed to `find_package_handle_standard_args` (CARVE) does
      not match the name of the calling package (Carve).  This can lead to
      problems in calling code that expects `find_package` result variables
      (e.g., `_FOUND`) to follow a certain pattern.
    Call Stack (most recent call first):
      cmake/FindCarve.cmake:30 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
      cmake/FindAllDependencies.cmake:101 (FIND_PACKAGE)
      Settings.cmake:24 (FIND_PACKAGE)
      CMakeLists.txt:5 (INCLUDE)
    This warning is for project developers.  Use -Wno-dev to suppress it.
    
    -- Carve library cannot be found.  Consider set CARVE_PATH environment variable (missing: CARVE_INCLUDE_DIRS CARVE_LIBRARIES)
    -- BSP library cannot be found.  Consider set BSP_PATH environment variable (missing: BSP_INCLUDE_DIRS BSP_LIBRARIES)
    CMake Warning (dev) at /usr/local/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:272 (message):
      The package name passed to `find_package_handle_standard_args` (UMFPACK)
      does not match the name of the calling package (Umfpack).  This can lead to
      problems in calling code that expects `find_package` result variables
      (e.g., `_FOUND`) to follow a certain pattern.
    Call Stack (most recent call first):
      cmake/FindUmfpack.cmake:77 (find_package_handle_standard_args)
      cmake/FindAllDependencies.cmake:111 (FIND_PACKAGE)
      Settings.cmake:24 (FIND_PACKAGE)
      CMakeLists.txt:5 (INCLUDE)
    This warning is for project developers.  Use -Wno-dev to suppress it.
    
    CMake Warning (dev) at /usr/local/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:272 (message):
      The package name passed to `find_package_handle_standard_args` (CHOLMOD)
      does not match the name of the calling package (Cholmod).  This can lead to
      problems in calling code that expects `find_package` result variables
      (e.g., `_FOUND`) to follow a certain pattern.
    Call Stack (most recent call first):
      cmake/FindCholmod.cmake:90 (find_package_handle_standard_args)
      cmake/FindAllDependencies.cmake:116 (FIND_PACKAGE)
      Settings.cmake:24 (FIND_PACKAGE)
      CMakeLists.txt:5 (INCLUDE)
    This warning is for project developers.  Use -Wno-dev to suppress it.
    
    CMake Warning (dev) at /usr/local/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:272 (message):
      The package name passed to `find_package_handle_standard_args` (METIS) does
      not match the name of the calling package (Metis).  This can lead to
      problems in calling code that expects `find_package` result variables
      (e.g., `_FOUND`) to follow a certain pattern.
    Call Stack (most recent call first):
      cmake/FindMetis.cmake:35 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
      cmake/FindAllDependencies.cmake:121 (FIND_PACKAGE)
      Settings.cmake:24 (FIND_PACKAGE)
      CMakeLists.txt:5 (INCLUDE)
    This warning is for project developers.  Use -Wno-dev to suppress it.

I also tried to install it based on the instructions here https://pymesh.readthedocs.io/en/latest/installation.html but also that did not succeed.

Appreciate any help on this matter.

Best. Jens

[francescomilano172]

Hi @jsll,

Thanks for reporting the issue. I've tried reproducing it on different computers with no previous installations, but the installation went through successfully. What setup are you using (OS, python version in the virtualenv, exact CMake version)?

Also, I'm not sure if it's necessary, but did you try again after installing the system dependencies mentioned in the PyMesh documentation?

apt-get install \
    libeigen3-dev \
    libgmp-dev \
    libgmpxx4ldbl \
    libmpfr-dev \
    libboost-dev \
    libboost-thread-dev \
    libtbb-dev \
    python3-dev

Best, Francesco

[jsll]

Thanks for a swift reply. The errors are indeed very strange. Everything else installes nicely except pymesh. Below are the requested information:

• cmake version 3.17.2
• Python version Python 3.6.9
• OS version: Ubuntu 18.04 Bionic Beaver

I have all the dependencies in PyMesh installed.

[francescomilano172]

Strange indeed, I tried using CMake 3.17.2 and PyMesh also installs without problems on my side. Maybe a few things to double check:

• Are you running the pip install command in a virtualenv?
• I suspect that the above are just warnings, and although I have no displayed warnings at all it could be that the actual error that breaks the build is somewhere else. Could you post the complete output?
• Just to be sure, could you try installing CMake locally instead of using the system-wide installation, and then add your local install to PATH and CMAKE_PREFIX_PATH (as in the answer here) before running pip install git+git://github.com/PyMesh/PyMesh.git@93d182c0a7cee446e89fac74033347d900054af4?

[mganglb]

i am gonna take the chance to ask in this issue my related question. #hatersgonnahate

Does PyMesh play a huge role in the pipeline, what is it used for? (i had no look at the code so far). In the past i already had problems building PyMesh and atm i am working on a Windows machine.

best wishes mgangl

[francescomilano172]

Hi @mganglb, no, it doesn't play a huge role in the pipeline. We use PyMesh just because it avoids the need to reimplement some functions that we use to process the meshes (loading/saving, conversion to graph-like structure, etc.).

Best, Francesco

[mganglb]

@francescomilano172 thx a lot for the fast answer, i am gonna have a look at it on the we. At the moment i am bound to an Windows workstation, that's why pymesh is for me kind of complicated. (Beside using docker)

best regards mgangl an enthusiastic 3d-deeplearning noob