Hi! I am new to nlopt and just trying to get it up and running. I have encountered several problems with the build system and think that they are worth reporting. Maybe I am doing something wrong, in this case I would appreciate your advice...
1) Inability to install Python bindings in a pre-defined virtualenv
Basically, I am using a standard virtualenvwrappers-based setup where a
binary Python interpreter that I have in /opt is used in several
virtualenvs sitting in $HOME/.virtualenv.
I switch into the required virutualenv (workon mle) and then execute the
following in order to build and install nlopt:
VE=.virtualenv/mle
./configure \
--prefix=/opt/nlopt \
--enable-shared \
--enable-static \
--with-cxx \
--without-guile \
--without-octave \
--without-matlab \
--with-python
PYTHON_PREFIX=$HOME/$VE \
PYTHON_PREFIX=$HOME/$VE/bin \
make install
(see log attached)
However, contrarily to what I would have expected, the Python bindings
are installed in /opt/nlopt/lib/python2.7/site-packages instead of
$HOME/.virtualenv/mle/lib/python2.7/site-packages .
I can symlink them for now, but it would be nice to know how to actually
override / specify Python prefix.
2) If I ./configure --with-mthreads it breaks things. I don't know if it
expected behavior or not, so I classify it as a problem. The reason why
I wanted to use mthreads was because I believed that "thread safe" is
good :-) that is, no particular reason.
Thanks for your time and Happy New Year!
--
Sincerely yours,
Yury V. Zaytsev
nlopt-virutualenv.log.gz
Description: GNU Zip compressed data
nlopt-mthreads.tar.gz
Description: application/compressed-tar
_______________________________________________ NLopt-discuss mailing list [email protected] http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/nlopt-discuss
