On 05/13/13 03:56, xunxun wrote:
> 于 2013/5/10 星期五 17:17, Jacek Caban 写道:
>> On 05/10/13 11:11, xunxun wrote:
>>> 于 2013/5/9 星期四 10:40, xunxun 写道:
于 2013/5/9 星期四 6:27, Jacek Caban 写道:
> On 5/8/13 7:27 AM, xunxun wrote:
>> 于 2013/1/21 星期一 21:07, Kai Tietz 写道:
>>> 2013/1/21 Jacek Cab
于 2013/5/10 星期五 17:17, Jacek Caban 写道:
> On 05/10/13 11:11, xunxun wrote:
>> 于 2013/5/9 星期四 10:40, xunxun 写道:
>>> 于 2013/5/9 星期四 6:27, Jacek Caban 写道:
On 5/8/13 7:27 AM, xunxun wrote:
> 于 2013/1/21 星期一 21:07, Kai Tietz 写道:
>> 2013/1/21 Jacek Caban :
>>> On 01/21/13 13:39, JonY wrot
2013/5/10 Jacek Caban :
> On 05/10/13 11:11, xunxun wrote:
>> 于 2013/5/9 星期四 10:40, xunxun 写道:
>>> 于 2013/5/9 星期四 6:27, Jacek Caban 写道:
On 5/8/13 7:27 AM, xunxun wrote:
> 于 2013/1/21 星期一 21:07, Kai Tietz 写道:
>> 2013/1/21 Jacek Caban :
>>> On 01/21/13 13:39, JonY wrote:
On
On 05/10/13 11:11, xunxun wrote:
> 于 2013/5/9 星期四 10:40, xunxun 写道:
>> 于 2013/5/9 星期四 6:27, Jacek Caban 写道:
>>> On 5/8/13 7:27 AM, xunxun wrote:
于 2013/1/21 星期一 21:07, Kai Tietz 写道:
> 2013/1/21 Jacek Caban :
>> On 01/21/13 13:39, JonY wrote:
>>> On 1/21/2013 09:43, Herb Thompson wr
于 2013/5/9 星期四 10:40, xunxun 写道:
> 于 2013/5/9 星期四 6:27, Jacek Caban 写道:
>> On 5/8/13 7:27 AM, xunxun wrote:
>>> 于 2013/1/21 星期一 21:07, Kai Tietz 写道:
2013/1/21 Jacek Caban :
> On 01/21/13 13:39, JonY wrote:
>> On 1/21/2013 09:43, Herb Thompson wrote:
>>> Q: Why do some 32-bit MinGW-
于 2013/5/9 星期四 6:27, Jacek Caban 写道:
On 5/8/13 7:27 AM, xunxun wrote:
于 2013/1/21 星期一 21:07, Kai Tietz 写道:
2013/1/21 Jacek Caban :
On 01/21/13 13:39, JonY wrote:
On 1/21/2013 09:43, Herb Thompson wrote:
Q: Why do some 32-bit MinGW-w64 applications fail with '...
_vswprintf
could not be locat
On 5/8/13 7:27 AM, xunxun wrote:
> 于 2013/1/21 星期一 21:07, Kai Tietz 写道:
>> 2013/1/21 Jacek Caban :
>>> On 01/21/13 13:39, JonY wrote:
On 1/21/2013 09:43, Herb Thompson wrote:
> Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf
> could not be located in the dynamic
于 2013/1/21 星期一 21:07, Kai Tietz 写道:
> 2013/1/21 Jacek Caban :
>> On 01/21/13 13:39, JonY wrote:
>>> On 1/21/2013 09:43, Herb Thompson wrote:
Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf
could not be located in the dynamic link library msvcrt.dll' on Windows
On Wed, Jan 23, 2013 at 3:22 AM, Ruben Van Boxem wrote:
> 2013/1/23 Xiaofan Chen
>>
>> On Wed, Jan 23, 2013 at 2:58 PM, Jim Michaels wrote:
>> >
>> > and, alas, microsoft has made sp2 unavailable and xp next year is
>> > support
>> > EOL except for embedded. so SP1 users (like me) are out of luck
2013/1/23 Xiaofan Chen
> On Wed, Jan 23, 2013 at 2:58 PM, Jim Michaels wrote:
> >
> > and, alas, microsoft has made sp2 unavailable and xp next year is
> support
> > EOL except for embedded. so SP1 users (like me) are out of luck unless
> they
> > have already downloaded and burned a copy of SP
On Wed, Jan 23, 2013 at 2:58 PM, Jim Michaels wrote:
>
> and, alas, microsoft has made sp2 unavailable and xp next year is support
> EOL except for embedded. so SP1 users (like me) are out of luck unless they
> have already downloaded and burned a copy of SP2 and SP3. after EOL, updates
> will no
: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll
on XP SP1
>2013/1/21 Jacek Caban :
>> On 01/21/13 13:39, JonY wrote:
>>> On 1/21/2013 09:43, Herb Thompson wrote:
>>>> Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf
&g
2013/1/21 Jacek Caban :
> On 01/21/13 13:39, JonY wrote:
>> On 1/21/2013 09:43, Herb Thompson wrote:
>>> Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf
>>> could not be located in the dynamic link library msvcrt.dll' on Windows
>>> XP SP1?
>>>
>>> A: For C++, MinGW-w64 imple
On 01/21/13 13:39, JonY wrote:
> On 1/21/2013 09:43, Herb Thompson wrote:
>> Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf
>> could not be located in the dynamic link library msvcrt.dll' on Windows
>> XP SP1?
>>
>> A: For C++, MinGW-w64 implements 'vswprintf (wchar_t *__s
On 1/21/2013 09:43, Herb Thompson wrote:
> Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf
> could not be located in the dynamic link library msvcrt.dll' on Windows
> XP SP1?
>
> A: For C++, MinGW-w64 implements 'vswprintf (wchar_t *__stream, const
> wchar_t *__format, __
I'd like to suggest the following Q&A for the FAQ:
--//--
Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf
could not be located in the dynamic link library msvcrt.dll' on Windows
XP SP1?
A: For C++, MinGW-w64 implements 'vswprintf (wchar_t *__stream, const
wchar_t *__for
On 5/15/2010 11:34, Jim Michaels wrote:
> one easy thing you could include with the compiler is a batch file which sets
> the environment variables for the compiler. put it in the bin directory for
> consistency.
>
> the variables that need to be set (I think) at least, are
> OBJC_INCLUDE_PATH
>
one easy thing you could include with the compiler is a batch file which sets
the environment variables for the compiler. put it in the bin directory for
consistency.
the variables that need to be set (I think) at least, are
OBJC_INCLUDE_PATH
C_INCLUDE_PATH
INCLUDE_PATH
CPATH
CPLUS_INCLUDE_PATH
18 matches
Mail list logo
