[lxc-devel] Static bulding of LXC tools (was: Re: Duplicate definitions of `lxc_log_define`)

[Daniel Lezcano]

Ciprian Dorin, Craciun wrote:

[ ... ]

> From 2bfc3d1be1715d582f7d319580d49723ff913d99 Mon Sep 17 00:00:00 2001
> From: Ciprian Dorin, Craciun <ciprian at volution.ro>
> Date: Sun, 10 Jan 2010 14:22:47 +0200
> Subject: [PATCH 2/2] Added options for building (enabling / disabling:
> static / shared libraries and linking).
> 
> Added the following options for `./configure` script:
>  * `--enable-shared` / `--disable-shared`, that instructs
>   if the (dynamic) `liblxc.so` is getting built and installed;
>  * `--enable-static` / `--disable-static`, that instructs
>   if the (static) `liblxc.a` is getting built and installed;
>  * `--enable-static-linking` that instructs if
>   the resulting executables are statically linked against `liblxc.a`;
> 
> There are also sensible defaults:
>  * `static` is by default `no`;
>  * `shared` is by default the negation of `static`;
>  * `static-linking` is by default equal with `static`;
> 
> As a consequence of the defaults there are the following scenarios:
>  * none of these options are specified => the build behaves exectly
> like before the patch;
>  * `--enable-static` => static linking, shared libraries are not built;
>  * `--enable-static --enable-shared` => we build both libraries, but
> we statically link;
>  * `--enable-static-linking` => static linking, but also the shared
> library is installed;

Hi Ciprian,

Why do we need such combination options, with --enable-static we make 
everything static. If the user neeeds to have shared, then it should 
rerun the configure without this option, no ?