[sleuthkit-developers] [ sleuthkit-Bugs-3584744 ] tsk_init_lock and tsk_deinit_lock not exported

[SourceForge.net <no...@so...>]

Bugs item #3584744, was opened at 2012-11-06 05:16
Message generated for change (Comment added) made by jbmetz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=477889&aid=3584744&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: Joachim Metz (jbmetz)
Assigned to: Nobody/Anonymous (nobody)
Summary: tsk_init_lock and tsk_deinit_lock not exported

Initial Comment:
Issue concerning TSK 4.0.0 API

The functions tsk_init_lock and tsk_deinit_lock are not exported in tsk3.h but they are necessary when creating a custom Img info object as in pytsk.
Please add them or add other functions to set/release the locks for custom img info objects.

----------------------------------------------------------------------

>Comment By: Joachim Metz (jbmetz)
Date: 2012-11-12 10:35

Message:
The idea of pytsk is to wrap python calls in an IMG info object, and allow
to extend the object in python.
Therefore it needs to control the locks. For now I've just added the
function calls. And build pytsk statically. 
This does not allow me to build against a DLL version.

----------------------------------------------------------------------

Comment By: Brian Carrier (carrier)
Date: 2012-11-12 10:30

Message:
Hi Joachim,

The theory was that if you are extending TSK, you would use tsk_base_i.h. 
tsk_base.h is really just if you want to use the library from another
program.  Does that work?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=477889&aid=3584744&group_id=55685