-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libboost required?! #87
Comments
Dne 22. 07. 22 v 16:10 Egbert napsal(a):
Over here at embedded Linux building the latest LVM2 requires |libboost|?!
So I noticed that I could stop using |libboost| by a compiler flag but....
Ummmmm, we did require the use of boost include before introducing |thin|
provisioning, right?
If so, can we break away from libboost and its mandatory development include
header files of libboost if THIN were disabled?
lvm2 is not using libboost.
devicemapper persistent data package (containing tools like cache_check,
thin_check...) does use this C++ library (for now - it's going to be soon
released as 'Rust' package.
So not sure what you are building or trying to use - but I'm pretty sure lvm2
itself does NOT use any C++ library for anything.
Although if you want to use thin/cache... you likely should use d-m-p-d
packages or otherwise you might end with unrecoverable situations....
(As lvm2 calls these tools via 'exec').
Regards
Zdenek
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Over here at embedded Linux building, the latest LVM2 requires
libboost
?!So I noticed that I could stop using
libboost
by a link flag to exclude the library but....Ummmmm, we did not require the use of boost include file before the LVM team introduced
thin
provisioning, right?If so, can we break away from boost include files (as well as the
libboost.so
) if THIN were disabled by compiler flag?Rationale
Primary reason is that
libboost
is a beast on limited storage space (as well as a beast during compiling and linking).The text was updated successfully, but these errors were encountered: