summaryrefslogtreecommitdiffstats
path: root/tools/lvm2cmdline.h
diff options
context:
space:
mode:
authorDave Wysochanski <dwysocha@redhat.com>2008-12-18 05:27:17 +0000
committerDave Wysochanski <dwysocha@redhat.com>2008-12-18 05:27:17 +0000
commit02961979994ceb2ce2e38f79ea4b5719faf3fb42 (patch)
tree7177cffb185d8317bf8a5e1120562024c71b3a88 /tools/lvm2cmdline.h
parentc5c13fe77627ef0329d1022c6b3daab99decd258 (diff)
downloadlvm2-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 'tools/lvm2cmdline.h')
-rw-r--r--tools/lvm2cmdline.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/tools/lvm2cmdline.h b/tools/lvm2cmdline.h
index f1741792..f4855e73 100644
--- a/tools/lvm2cmdline.h
+++ b/tools/lvm2cmdline.h
@@ -26,12 +26,12 @@ struct cmdline_context {
int interactive;
};
-int lvm2_main(int argc, char **argv, unsigned is_static);
+int lvm2_main(int argc, char **argv);
void *cmdlib_lvm2_init(unsigned is_static);
void lvm_fin(struct cmd_context *cmd);
-struct cmd_context *init_lvm(unsigned is_static);
+struct cmd_context *init_lvm(void);
void lvm_register_commands(void);
int lvm_split(char *str, int *argc, char **argv, int max);
int lvm_run_command(struct cmd_context *cmd, int argc, char **argv);