Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenVDB-3.1.0: Makefile doesn't respect certain options revert back to default. #65

Closed
dracwyrm opened this issue Jun 3, 2016 · 2 comments

Comments

@dracwyrm
Copy link
Contributor

dracwyrm commented Jun 3, 2016

When compiling with make, certain options are not properly used.

The full command line used is this:
make -j2 rpath=no shared=yes DESTDIR=/var/tmp/portage/media-gfx/openvdb-3.1.0/image/usr HFS=/usr HT=/usr HDSO=/usr/lib64 GLFW_INCL_DIR=/usr/lib64 GLFW_LIB_DIR=/usr/lib64 BLOSC_INCL_DIR=/usr/include BLOSC_LIB_DIR=/usr/lib64 EPYDOC= DOXYGEN= LIBOPENVDB_RPATH= CPPUNIT_INCL_DIR=/usr/include/cppunit CPPUNIT_LIB_DIR=/usr/lib64 LOG4CPLUS_INCL_DIR=/usr/include/log4cplus LOG4CPLUS_LIB_DIR=/usr/lib64 PYTHON_VERSION=3.5 PYTHON_INCL_DIR=/usr/include/python3.5m PYCONFIG_INCL_DIR=/usr/include/python3.5m PYTHON_LIB_DIR=/usr/lib64/libpython3.5m.so PYTHON_LIB=-lpython3.5m NUMPY_INCL_DIR=/usr/lib64/python3.5/site-packages/numpy/core/include/numpy BOOST_PYTHON_LIB_DIR=/usr/lib64 BOOST_PYTHON_LIB=-lboost_python-3.5

However, DESTDIR, EPYDOC, and DOXYGEN revert back to the default settings in Makefile. The other options seem to work, as the respected libraries are found. How do I get the Make file to properly respect the options passed to it on the make line?

Thanks,
Jon

@dracwyrm
Copy link
Contributor Author

dracwyrm commented Jun 3, 2016

During the install phase, the variable information gets lost, as you can see here:

>>> Install openvdb-3.1.0 into /var/tmp/portage/media-gfx/openvdb-3.1.0/image/ category media-gfx
make -j2 DESTDIR=/var/tmp/portage/media-gfx/openvdb-3.1.0/image/ install 
Generating documentation because of doxygen-config and others
echo 'OUTPUT_DIRECTORY=./doc' | cat doxygen-config - | doxygen - > /dev/null
Generating Python module documentation because of pyopenvdb.so libopenvdb.so.3.1
pydocdir=doc/html/python; \
mkdir -p ${pydocdir}; \
echo "Created ${pydocdir}"; \
export LD_LIBRARY_PATH=:/var/tmp/portage/media-gfx/openvdb-3.1.0/work/openvdb; \
export PYTHONPATH=:/var/tmp/portage/media-gfx/openvdb-3.1.0/work/openvdb; \
    epydoc --html --html-dir ${pydocdir} pyopenvdb > /dev/null
Created doc/html/python
/bin/bash: line 5: epydoc: command not found

The install phase should use the same variable information that was passed to it on the initial make command.

@dracwyrm
Copy link
Contributor Author

dracwyrm commented Jun 5, 2016

Submitted PR. Hard coded install path was causing access violation.

@dracwyrm dracwyrm closed this as completed Jun 5, 2016
danrbailey pushed a commit to danrbailey/openvdb that referenced this issue Oct 16, 2016
OpenVDB Points now requires a C++11 compiler
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant