On 04/28/2014 09:30 PM, Justin Ross wrote:
On Mon, Apr 28, 2014 at 4:27 PM, Gordon Sim <[email protected]> wrote:
Can SYSINSTALL_BINDINGS=ON not be automatically inferred if no
CMAKE_INSTALL_PREFIX is specified? Or does CMAKE_INSTALL_PREFIX always
have
a value, even if not set explicitly?
That would overwrite OS-reserved file locations.
That's what make install (without an explicit prefix) always does, isn't
it?
If I don't specify a prefix, I expect things to be installed into the
system wide default locations for whatever it is. If I specify a prefix, I
expect to to be relative to that and expect to have to set various path
variables to locate 'my' install.
No, the default prefix is typically /usr/local, and indeed /usr/local is
set aside for this use. For instance, setup.py install by default installs
with the prefix /usr/local on unix machines.
Yes, I wasn't suggesting changing the default.
So are you saying that SYSINSTALL_BINDINGS doesn't use the 'default',
but overrides that? If so then I agree with Fraser that the language in
the warning is confusing. (Since it sounds like the 'non-standard
'approach is used by default unless the 'standard' one is explicitly
selected.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
