Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3A560012.9070706@redhat.com>
Date: Fri, 05 Jan 2001 12:10:42 -0500
From: Dave Brolley <brolley AT redhat DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; m18) Gecko/20001108 Netscape6/6.0
X-Accept-Language: en
MIME-Version: 1.0
To: Christopher Faylor <cgf AT redhat DOT com>
CC: cygwin AT cygwin DOT com, gcc AT gcc DOT gnu DOT org
Subject: Re: #including <tchar.h> using gcc on Cygwin
References: <3A54FC85 DOT 9030104 AT redhat DOT com> <4 DOT 3 DOT 1 DOT 2 DOT 20010104174839 DOT 022642d0 AT pop DOT ma DOT ultranet DOT com> <20010104183600 DOT A24434 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Thanks to all to responded. It looks like all that is wanted is a macro 
named __T(x) which takes a string literal and produces either a wide 
version of it or just the original literal, depending on whether the 
application is Unicode enabled or not. The mingw32 version of <tchar.h> 
defines similar macros named _T and _TEXT. The __T macro is only used in 
one file of the application, so I'll work around this for now until I 
can find out from the owner of the code whether it is really necessary 
or not.

Thanks again,
Dave

Christopher Faylor wrote:

> On Thu, Jan 04, 2001 at 05:54:52PM -0500, Larry Hall (RFK Partners, Inc) wrote:
> 
>> At 05:43 PM 1/4/2001, Dave Brolley wrote:
>> 
>>> Hi,
>>> 
>>> I'm trying to use gcc to compile an application on Cygwin which #includes <tchar.h>. In searching my system, I see a tchar.h in /usr/include/mingw32, but the compiler doesn't seem to be finding it. Is it safe for me to add -I/usr/include/mingw32 to my compile options, or is there a more appropriate way to pick up this header?
>>> 
>>> BTW, what does mingw32 stand for anyway? :-)
>> 
>> It may be OK to do this, but it will be plain luck if it works in this 
>> case.  Mingw32 stands for the Mingw initiative, that seeks to provide 
>> a compiler toolset to produce executables that don't rely on cygwin1.dll.
>> See www.mingw.org for more details.  This directory exists in Cygwin because
>> the compiler delivered with Cygwin supports cross-compiling to Mingw.  To
>> invoke this cross compiler, use the -mno-cygwin flag.  If you do so, you 
>> should find that tchar.h is found, since the compiler will look at this 
>> path for cross compiling purposes.  You must make sure that you don't need
>> the POSIX functions only available in Cygwin though if you enable this flag,
>> since you can't have both Cygwin and Mingw together.  That's why I said 
>> initially that you can try doing what you describe, but if it doesn't work
>> or causes problems, you're on your own!;-)
> 
> 
> Actually, I would not go so far as to say it may be OK.  It is really a
> bad idea to include /usr/include/mingw32 unless you are building mingw
> applications.  You'll get into all sorts of problems if you try to mix
> mingw and cygwin together.  They are mutually exclusive.
> 
> If you are compiling a strict Windows app, though, -mno-cygwin is the
> right thing to do.
> 
> cgf
> 
> 
> 


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple