Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Mon, 8 Dec 2003 15:54:36 +0100
From: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
Reply-To: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
Organization: Esse keine toten Tiere
X-Priority: 3 (Normal)
Message-ID: <311597174926.20031208155436@familiehaase.de>
To: "'Cygwin List'" <cygwin AT cygwin DOT com>
Subject: Re: [PATHC] for w32api/sql.h (was: Re: <w32api/sql.h> broken?)
In-Reply-To: <271586644554.20031208125906@familiehaase.de>
References: <Law9-OE2122ZhCl8aii000026b5 AT hotmail DOT com>
 <271586644554 DOT 20031208125906 AT familiehaase DOT de>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit

Rafael wrote:

I've thought about doing that, but mingw and Cygwin use the same w32api
headers, and mingw (aka gcc -mno-cygwin) does not understand
<w32api/foo>. However, this works:

--- sql.h       2003-12-08 04:20:17.328125000 -0800
+++ sql.h.new   2003-12-08 04:19:36.718750000 -0800
@@ -10,7 +10,11 @@
 #ifndef ODBCVER
 #define ODBCVER 0x0351
 #endif
-#include <sqltypes.h>
+#ifdef __CYGWIN__
+       #include <w32api/sqltypes.h>
+#else
+       #include <sqltypes.h>
+#endif
 #define SQL_ACCESSIBLE_PROCEDURES 20
 #define SQL_ACCESSIBLE_TABLES 19
 #define SQL_ALL_TYPES 0


This looks to be more correct than the other patch I posted earlier.



-- 
=^..^=                                     http://nyckelpiga.de/donate.html


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/