From: SourceForge.net <no...@so...> - 2006-10-14 02:20:11
|
Bugs item #1557722, was opened at 2006-09-13 02:10 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1557722&group_id=2435 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: w32api Group: Waiting User Response >Status: Closed Resolution: Invalid Priority: 5 Submitted By: Andriy Syrovenko (andriys) Assigned to: Earnie Boyd (earnie) Summary: Include guard problem while compiling OleDB apps. Initial Comment: The include guard defined in the winbase.h in MinGW differs from the one found in Microsoft's (and Borland's, and possibly others) version of winbase.h. This causes troubles when compiling OleDB application, namely applications speaking to the MS SQL Server. MinGW's winbase.h header defines the following include macro: _WINBASE_H while the Microsoft's 'oledb.h' expects the following macro to be defined if 'winbase.h' has already been included: _WINBASE_ The trivial patch is attached. Thanks. ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2006-10-13 19:20 Message: Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 30 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2006-09-13 05:58 Message: Logged In: YES user_id=15438 So, if I'm understanding you correctly, you are mixing in MS header oledb.h with MinGW headers? Is this correct? If so, then you're choice is to define _WINBASE_ before you include oledb.h yourself. I don't see this a patch that is necessary for MinGW headers. Earnie ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1557722&group_id=2435 |