Hi again; I waited for a while but I didn't get any report on how well (or bad) the new twain header works while building on Windows. I am pretty sure the authors take care of GCC and most commercial compilers so the only special case is mingw32.
Ming32 is something that was indeed hacked into our old header so I adapted the code to suit our previous behavior and now that I have something robust I have committed it. I did everything I could to ensure this works but I am not perfect, and there has been little feedback, so please don't panic and let me know if something related with scanners changes. Pedro. --- On Sun, 10/16/11, Pedro Giffuni <[email protected]> wrote: > Date: Sunday, October 16, 2011, 8:30 PM > Hello; > > As you might have noticed I have been updating some > headers and libraries we use internally. I think it > is just logical to want to start working with modern > APIs. > > In the case of TWAIN, this is something that has evolved > quite a bit, the new versions add support for UNIX/linux > and Win64. Our older version had some support for ming32 > that the new header didn't have. > > I added the mingw32 support but I can't test it because > I don't use ming32. Of course, I also can't just break > the build to test the patch so I've added it to BZ > Bug 118517. > > Please give it a try and report or send patches through > bugzilla: this header could help improve support for > modern scanners in the future. > > cheers. > > Pedro. >
