Implicit3DUnderstanding: Error in building the project

Hi @chengzhag ,

I got the following error while building the project. Seems like there are some missing files.

Building pyrender...
Run: cd external/mesh_fusion/librender && /home/user/anaconda3/envs/pytorch11_py3_Im3D/bin/python setup.py build_ext --inplace
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
In file included from /home/user/anaconda3/envs/pytorch11_py3_Im3D/lib/python3.6/site-packages/numpy/core/include/numpy/ndarraytypes.h:1832:0,
                 from /home/user/anaconda3/envs/pytorch11_py3_Im3D/lib/python3.6/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
                 from /home/user/anaconda3/envs/pytorch11_py3_Im3D/lib/python3.6/site-packages/numpy/core/include/numpy/arrayobject.h:4,
                 from pyrender.cpp:531:
/home/user/anaconda3/envs/pytorch11_py3_Im3D/lib/python3.6/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
 #warning "Using deprecated NumPy API, disable it with " \
  ^
In file included from pyrender.cpp:534:0:
offscreen.h:4:21: fatal error: GL/glew.h: No such file or directory
compilation terminated.
error: command 'gcc' failed with exit status 1
Traceback (most recent call last):
  File "project.py", line 158, in <module>
    globals()[args.work](args)
  File "project.py", line 120, in build
    subprocess.check_output(cmd, shell=True)
  File "/home/user/anaconda3/envs/pytorch11_py3_Im3D/lib/python3.6/subprocess.py", line 356, in check_output
    **kwargs).stdout
  File "/home/user/anaconda3/envs/pytorch11_py3_Im3D/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command 'cd external/mesh_fusion/librender && /home/user/anaconda3/envs/pytorch11_py3_Im3D/bin/python setup.py build_ext --inplace' returned non-zero exit status 1.

It seems there is no directory called GL. Hence, any reference to headers included in it would probably throw an error.

Would appreciate your help with this.

~Cheers!

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Comments: 35 (17 by maintainers)

Most upvoted comments

Hi @metro-smiles,

From what I understand, the mesh_fusion/fusion.py does import libfusiongpu when use_gpu set to True. But further experiments indicate that GPU is truely not used (with the help of nvidia-smi) and there is no speed difference between libfusiongpu and libfusioncpu. It seems like that there is a problem with mesh_fusion lib, which I did not notice and cannot provide further help.

However, the preprocessing of Pix3D is accelerated with multi-thread, which can be done in less than hour. Thus the problem seems not very significant.

Thanks for your summary for the compiling problem. We updated two recent commits to solving it.

Hi @emirhanKural,

We use the detection results provided by Total3D and Coop. However, the 2D detector is not included in their code.

The detections.json of the demo is converted from the provided detections. If you want to test on your own data, you have to either fine-tune a 2D detector on SUN-RGBD or fine-tune it on your own dataset and map the output categories.