Return-Path: 
 <users-return-10464-apmail-qpid-users-archive=qpid.apache.org@qpid.apache.org>
X-Original-To: apmail-qpid-users-archive@www.apache.org
Delivered-To: apmail-qpid-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id A18B710CD2
	for <apmail-qpid-users-archive@www.apache.org>;
 Wed, 30 Apr 2014 02:13:27 +0000 (UTC)
Received: (qmail 66613 invoked by uid 500); 30 Apr 2014 02:13:27 -0000
Delivered-To: apmail-qpid-users-archive@qpid.apache.org
Received: (qmail 66584 invoked by uid 500); 30 Apr 2014 02:13:26 -0000
Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@qpid.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@qpid.apache.org>
List-Post: <mailto:users@qpid.apache.org>
List-Id: <users.qpid.apache.org>
Reply-To: users@qpid.apache.org
Delivered-To: mailing list users@qpid.apache.org
Received: (qmail 66576 invoked by uid 99); 30 Apr 2014 02:13:26 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Apr 2014 02:13:26 +0000
X-ASF-Spam-Status: No, hits=-5.0 required=5.0
	tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of aconway@redhat.com designates
 209.132.183.28 as permitted sender)
Received: from [209.132.183.28] (HELO mx1.redhat.com) (209.132.183.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Apr 2014 02:13:22 +0000
Received: from int-mx11.intmail.prod.int.phx2.redhat.com
 (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s3U2CvFF006729
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK)
	for <users@qpid.apache.org>; Tue, 29 Apr 2014 22:12:57 -0400
Received: from [10.3.113.20] (ovpn-113-20.phx2.redhat.com [10.3.113.20])
	by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id
 s3U2CuY4018639
	for <users@qpid.apache.org>; Tue, 29 Apr 2014 22:12:57 -0400
Message-ID: <1398823976.17599.47.camel@localhost>
Subject: How do you install qpid bits?
From: Alan Conway <aconway@redhat.com>
To: users <users@qpid.apache.org>
Date: Tue, 29 Apr 2014 22:12:56 -0400
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24
X-Virus-Checked: Checked by ClamAV on apache.org

The discussion about how make install should work has made me wonder,
how are people installing the various qpid bits?

Perhaps we can collect the different use cases and come up with some
simple, consistent behavior for all the various projects that will make
life easy for everyone.

Here's what I do: I install everything in /usr/local. I do not want to
ever clobber RPM installed files in /usr. Here's how I do it:

With a  qpid-proton checkout at $PROTON and
CMAKE_INSTALL_PREFIX=/usr/local (the default)

 cd $PROTON/<build-directory>; make install

With a qpid checkout at $QPID and CMAKE_INSTALL_PREFIX=/usr/local (the
default)

 cd $QPID/qpid/cpp/<build-directory>; make install
 cd $QPID/qpid/tools; ./setup.py install --prefix /usr/local
 cd $QPID/qpid/python; ./setup.py install --prefix /usr/local

And finally make sure to set up your environment:

export PATH="$PATH:/usr/local/sbin:/usr/local/bin"
export
PYTHONPATH="$PYTHONPATH:/usr/local/lib/proton/bindings/python:/usr/local/lib64/proton/bindings/python:/usr/local/lib/python2.7/site-packages:/usr/local/lib64/python2.7/site-packages"
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/lib64"





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org