diff options
| author | Dave Wysochanski <dwysocha@redhat.com> | 2008-12-18 05:27:17 +0000 |
|---|---|---|
| committer | Dave Wysochanski <dwysocha@redhat.com> | 2008-12-18 05:27:17 +0000 |
| commit | 02961979994ceb2ce2e38f79ea4b5719faf3fb42 (patch) | |
| tree | 7177cffb185d8317bf8a5e1120562024c71b3a88 /lib/lvm2.h | |
| parent | c5c13fe77627ef0329d1022c6b3daab99decd258 (diff) | |
| download | lvm2-02961979994ceb2ce2e38f79ea4b5719faf3fb42.tar.gz lvm2-02961979994ceb2ce2e38f79ea4b5719faf3fb42.tar.xz lvm2-02961979994ceb2ce2e38f79ea4b5719faf3fb42.zip | |
Create global is_static() to eliminate from the library init function.
Very simple / crude method of removing 'is_static' from initialization.
Why should we require an application tell us whether it is linked
statically or dynamically to libLVM? If the application is linked
statically, but libraries exist and dlopen() calls succeed, why
do we care if it's statically linked?
Diffstat (limited to 'lib/lvm2.h')
| -rw-r--r-- | lib/lvm2.h | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -24,7 +24,7 @@ */ struct arg; struct cmd_context; -struct cmd_context *create_toolcontext(unsigned is_static, unsigned is_long_lived); +struct cmd_context *create_toolcontext(unsigned is_long_lived); void destroy_toolcontext(struct cmd_context *cmd); /* @@ -37,7 +37,7 @@ lvm_handle_t lvm2_create(void); * NULL: Fail - unable to initialise handle. * non-NULL: Success - valid LVM2 handle returned */ -#define lvm2_create(X) create_toolcontext(0,1) +#define lvm2_create(X) create_toolcontext(1) /* * lvm2_destroy |