Menu

#121 tsk 3.1.0b1 does not build with libewf20091128 (api v2)

open
nobody
Other (13)
5
2009-12-22
2009-12-22
Marc Bown
No

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.

Discussion

  • Marc Bown

    Marc Bown - 2009-12-22

    Patch to tsk 3.1.0b1 to resolve issues with libewf20091128 compatibility

     
  • Brian Carrier

    Brian Carrier - 2009-12-24

    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).

     
  • Joachim Metz

    Joachim Metz - 2009-12-26

    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

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.