Re: [sleuthkit-users] more issues with mingw - and solutions

[Simson G. <si...@ac...>]

I'm using mingw. 

To answer your question below, mingw doesn't include zlib in the default distribution. It needs to be added---for example, by adding the zlib-dev package. Because zlib-dev is not present on other systems as well, you need to add it.

One of the reasons that AFF, TSK, and LIBEWF are all having problems with the growing plethora of compile platforms is that we frequently do not understand the #include structure of the various platforms.  I have invested considerable time in this over the past few months. I have learned:

1. Never use "u_char" ; it's not standard. Use uint8_t.
2. Likewise, don't use "u_long", use uint32_t.
3. Check for the presence of mingw with this:

#if !defined(__MINGW_H)

4. On Windows, always include <windows.h> and <winsock.h>
>> 
>> 
>> AC_CHECK_HEADERS([config_msc.h])
>> 
>> And the line in ewf.h needs to be changed to read:
>> 
>> #ifdef HAVE_CONFIG_MSC_H
>> #include <config_msc.h>
>> #endif
> 
> 
> That doesn't work though because configure.ac stuff isn't used on a Visual Studio build where config_msc.h is needed.  The real test is to include that only when it is a windows build and not mingw. I changed it to  _MSC_VER instead. 

That's a great fix.