On Wed, 2012-12-05 at 08:55 -0500, Rafael Schloming wrote:
> On Wed, Dec 5, 2012 at 8:18 AM, Darryl L. Pierce <dpie...@redhat.com> wrote:
> 
> > On Tue, Dec 04, 2012 at 05:24:25PM -0500, Andrew Stitcher wrote:
> > > On Thu, 2012-11-29 at 17:16 -0500, Darryl L. Pierce wrote:
> > > > I've pushed the Perl language bindings as well as the send/recv
> > examples
> > > > for using the qpid::proton::Messenger and qpid::proton::Message
> > classes.
> > >
> > > These changes break "make install" for a developer build installing in a
> > > non system location:
> > >
> > > ...
> > > --
> > > Installing:
> > /home/andrew/Work/proton/install/lib64/python2.7/site-packages/proton.pyo
> > > --
> > > Installing:
> > /home/andrew/Work/proton/install/lib64/python2.7/site-packages/_cproton.so
> > > -- Removed runtime path from
> > >
> > "/home/andrew/Work/proton/install/lib64/python2.7/site-packages/_cproton.so"
> > > -- Installing: /home/andrew/Work/proton/install/lib64/ruby/cproton.so
> > > -- Removed runtime path from
> > > "/home/andrew/Work/proton/install/lib64/ruby/cproton.so"
> > > -- Installing: /usr/lib64/perl5/libcproton_perl.so
> > > CMake Error at bindings/perl/cmake_install.cmake:44 (FILE):
> > >   file INSTALL cannot copy file
> > >   "/home/andrew/Work/proton/bld/bindings/perl/libcproton_perl.so" to
> > >   "/usr/lib64/perl5/libcproton_perl.so".
> > > Call Stack (most recent call first):
> > >   bindings/cmake_install.cmake:39 (INCLUDE)
> > >   cmake_install.cmake:137 (INCLUDE)
> > >
> > >
> > > It seems like this new stuff just ignores CMAKE_INSTALL_PREFIX.
> >
> > Yeah, it appears that the CMake configuration for Proton doesn't do what
> > Qpid's configuration did as far as prepending the install prefix to
> > directories. None of our language bindings seem to be doing this in
> > Proton.
> >
> 
> The other builds don't manually prepend the install prefix, however they
> still honor it where appropriate by using relative paths. Cmake will
> automatically prepend the install prefix for you if you just use a relative
> path. I'm not sure why the qpid build goes to the trouble of manually
> prepending it. IMHO that's a bit misleading as you generally only need to
> use absolute paths if you're trying to install something outside of the
> install root.

It is a bit surprising that the prefix is ignored if it is absolute but
honored if its relative. IMO if a prefix is specified it should be
honoured.


Reply via email to