[libvirt] Re: Works: libvirt client on OS X 10.5.6

[Schley Andrew Kutz]

Getting libvirt-java 0.2.1 to compile on OS X

- Set environment variables

   LIBVIRT_CFLAGS=-I/opt/libvirt-0.6.3/include
   LIBVIRT_LIBS=-L/opt/libvirt-0.6.3/lib

- Configure

./configure --prefix=/opt/libvirt-java-0.2.1 --with-java-home=$JAVA_HOME

- Compile

--  
-a

"Ideally, a code library must be immediately usable by naive  
developers, easily customized by more sophisticated developers, and  
readily extensible by experts." -- L. Stein

On May 7, 2009, at 11:50 PM, Schley Andrew Kutz wrote:

> Getting libvirt-0.6.3 (client) to compile on OS X
>
> - Use MacPorts to install gnutls (and its several dependencies)
>
> - Set environment variables:
>
>  export LDFLAGS="-L/opt/local/lib"
>  export CPPFLAGS="-I/opt/local/include"
>  export MACOSX_DEPLOYMENT_TARGET=10.4
>
> - Configure
>
> --prefix=/opt/libvirt/ --without-sasl --without-avahi --without- 
> polkit --without-python --without-xen --without-qemu --without-lxc -- 
> without-openvz --without-libvirtd --without-uml
>
> - Apply patches
>
>   src/pci.c
>
>      #ifndef MODPROBE
>      #define MODPROBE 0
>      #endif
>
>   src/virsh.c:5665
>
>      if (command_ret != 0 /* WEXITSTATUS (0) */) {
>
> - Compile
>
> The MACOSX_DEPLOYMENT_TARGET variable is very important, otherwise  
> you will get symbol errors when linking.
>
> -- 
> -a
>
> "Ideally, a code library must be immediately usable by naive  
> developers, easily customized by more sophisticated developers, and  
> readily extensible by experts." -- L. Stein
>