On 05/30/2013 02:32 PM, Darryl L. Pierce wrote:
On Thu, May 30, 2013 at 01:57:48PM +0100, Gordon Sim wrote:
Do you mean with using DESTDIR=$somedir ?
Using CMAKE_INSTALL_PREFIX.
I'm not seeing any install failures during packaging. The RPM packaging
system uses a non-standard location to install the bits before
generating the RPMs.
I see:
Install the project...
-- Install configuration: ""
-- Installing:
/home/gordon/qpid-releases/0.22rc6/TEST_INSTALL/share/doc/qpid-cpp-0.22/LICENSE
-- Installing:
/home/gordon/qpid-releases/0.22rc6/TEST_INSTALL/share/doc/qpid-cpp-0.22/NOTICE
-- Installing:
/home/gordon/qpid-releases/0.22rc6/TEST_INSTALL/share/qpid/qpid/qpid.i
-- Installing:
/home/gordon/qpid-releases/0.22rc6/TEST_INSTALL/share/qpid/qpid/swig_perl_typemaps.i
-- Installing:
/home/gordon/qpid-releases/0.22rc6/TEST_INSTALL/share/qpid/qpid/swig_python_typemaps.i
-- Installing:
/home/gordon/qpid-releases/0.22rc6/TEST_INSTALL/share/qpid/qpid/swig_ruby_typemaps.i
-- Installing:
/home/gordon/qpid-releases/0.22rc6/TEST_INSTALL/include/qmf/qmfengine.i
-- Installing:
/home/gordon/qpid-releases/0.22rc6/TEST_INSTALL/include/qmf/qmf2.i
-- Installing: /home/gordon/qpid-releases/0.22rc6/TEST_INSTALL/bin/qmf-gen
CMake Error at managementgen/cmake_install.cmake:48 (FILE):
file cannot create directory: /usr/lib/python2.7/site-packages/qmfgen.
These seem not to get installed into my required location as are the
earlier artefacts above.
Maybe need administrative privileges.
Call Stack (most recent call first):
cmake_install.cmake:60 (INCLUDE)
Ah, I see what you mean. This is how it's supposed to work. When
installing the bindings, those directories are determined by where the
language's site directories are located and not by the install prefix
set during the Cmake generation phase. This same case applies to Proton
as well.
To control where the files are installed, it's not recommended to use
the CMAKE_INSTALL_PREFIX but instead use DESTDIR=$someplace, which
installs everything relative to that directory.
Ok, I will do that. Thanks for the clarification!
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
