Closed blshkv closed 6 years ago
This is because you are building it with a stand-alone version of libfdata that does not export these functions.
As indicated before this is not the recommended approach
I have a strong opinion that this approach is the way to go. There are multiple packages which re-using the same libraries (cerror and bunch of others) and it totally make sense to compile them as shared libraries.
Back to the topic, you might not see warnings but the code could be not as good as other libraries. At least, I don't see such warnings with other 20 libc* libraries from your tree.
This is because this is WIP as you can see in https://github.com/libyal/libfdata/blob/master/include/libfdata.h.in#L1084 there are no libfdata_tree functions in the public api yet.
I have a strong opinion that this approach is the way to go. There are multiple packages which re-using the same libraries (cerror and bunch of others) and it totally make sense to compile them as shared libraries.
Again, at this point in time this is not recommended
ok, noted. I look forward for better times. Hopefully, you will improve it soon. It's just easier to support it this way. IMHO of cause.
Hopefully, you will improve it soon.
When time permits.
It's just easier to support it this way.
No its not, the approach you so strongly prefer, can lead to subtle hard to debug issues
No updates in a while closing issue seeing this is WIP
GCC (gcc-5.4.0) with -Wall should give the same results: