On Wed, Jun 25, 2014 at 11:12:52AM -0600, Eric Blake wrote:
On 06/25/2014 10:59 AM, Peter Krempa wrote:
> On 06/25/14 18:53, Eric Blake wrote:
>> Thanks to Dan's recent work in libvirt.git, it is much easier to
>> develop against uninstalled libvirt. Mention how.
>>
>> * README: More details.
>>
>> Signed-off-by: Eric Blake <eblake(a)redhat.com>
>> ---
>> README | 15 +++++++++++++++
>> 1 file changed, 15 insertions(+)
>>
>
> ACK,
Thanks; pushed.
FYI: I'm also using this (but considered it hackish enough to not
publish as a formal patch):
$ echo /GNUmakefile >> .git/info/exclude
$ cat GNUmakefile
# My hidden wrapper to preset things that I like...
include Makefile
export LD_LIBRARY_PATH=/home/eblake/libvirt/src/.libs/
export PKG_CONFIG_PATH=/home/eblake/libvirt/src/
$
Now all I have to do is run 'python setup.py build' to build against
installed libvirt, vs. 'make' to build against development libvirt, at
least for my machine.
It occurs to me that if we edit the 'run' script in libvirt GIT to
set that PKG_CONFIG_PATH setting, then you could build and test the
python bindings by doing
/home/eblake/libvirt/run python setup.py build
Or in your case with the make wrapper
/home/eblake/libvirt/run make
Regards,
Daniel
--
|:
http://berrange.com -o-
http://www.flickr.com/photos/dberrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|:
http://entangle-photo.org -o-
http://live.gnome.org/gtk-vnc :|