Bugs item #2919095, was opened at 2009-12-22 04:31
Message generated for change (Comment added) made by jbmetz
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=477889&aid=2919095&group_id=55685
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Marc Bown (inbowned)
Assigned to: Nobody/Anonymous (nobody)
Summary: tsk 3.1.0b1 does not build with libewf20091128 (api v2)
Initial Comment:
When libewf 20091128 is installed with api_v2 the function libewf_check_file_signature is different to versions prior to 20081013.
My C is terrible, but I've put together a patch which seems to work (the build errors go away and the tools appear to work on a number of test images). Please feel free to throw it out or to just correct my rubbish code.
----------------------------------------------------------------------
Comment By: Joachim Metz (jbmetz)
Date: 2009-12-26 11:27
Message:
Marc,
I have dubbed libewf's API v2 as experimental for the following reason.
I'm content with most of the function names but there are some that still
may change. Consider the current v2 api more of a preview.
FYI I'll first release a v2 alpha/beta version with (largely) backwards
compatibility. The idea is to remove HAVE_V2_API from that version. So a
better way is to have configure detect if the v2 functions are available or
the libtool version of the library which should be 2.
I (currently) have no intentions on changing the
libewf_check_file_signature v2 function. So the patch should be safe on
that part.
Joachim
----------------------------------------------------------------------
Comment By: Brian Carrier (carrier)
Date: 2009-12-24 17:25
Message:
The v2 API is still listed as "experimental". I have been waiting until the
APIs are part of an official release until I incorporate support for them
(in case they change again).
It looks like a patch could also use HAVE_V2_API to support both versions.
I am going to e-mail the libewf folks to see if they can make a more
LIBEWF specific definition (such as LIBEWF_HAVE_V2_API).
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=477889&aid=2919095&group_id=55685
|
