Some header-files and library-files are protected by Copy Right.
You can use every valid header-file with the MinGw stuff.
If the library contains only C-Code you can use the Microsoft *.lib-
File directy as input for the gnu-linker.
Craig Reagan wrote:
> I am working on an app that needs to use functions in
> odbcC32.dll, however, the import library 'libodbc32.a' seems
> to be out of data. I have a copy of the latest MSSDK and it
> basically has zero documentation on any deprecated functions
> related to ODBC data access. So I thought I would try to
> extract the information needed to build a new import library
> from the library supplied with the SDK which I was able to
> do with suprising ease. Now the problem of course is the
> headers need to be updated to be able to take advantage of
> all the new functions in this import library. That's not
> toooo much trouble but it did get me to thinking that it
> would be nice if I could just use MS's headers and be done
> with it. I also thought that I could then rebuild the
> entire set of import libs from the SDK and be completely up
> to date!
> So my question is, Is this a pipe dream? What
> barriers are there to be overcome in order to be able to use
> MS's headers as they are distributed with the SDK?
> Craig Reagan
> MinGW-users mailing list
> You may change your MinGW Account Options at:
Technische Universitaet Berlin, Germany
Uni.: +49 30 314 26 884
privat: +49 30 815 30 32
Handy: +49 173 20 10 696