On 25.04.2015 10:04, Kai Tietz wrote:
> 2015-04-25 6:41 GMT+02:00 LRN:
>> On 24.04.2015 3:00, LRN wrote:
>>> We have the prototype in the header (guarded as Vista-or-later), but no
>>> stub in
>>> the import library. I don't know how to fix that (.def files for implibs
>>> seem
>>> to be special
On 25.04.2015 11:44, LRN wrote:
> On 25.04.2015 11:23, LRN wrote:
>> On 25.04.2015 10:04, Kai Tietz wrote:
>>> 2015-04-25 6:41 GMT+02:00 LRN wrote:
On 24.04.2015 3:00, LRN wrote:
> We have the prototype in the header (guarded as Vista-or-later), but no
> stub in
> the import libra
On 25.04.2015 11:23, LRN wrote:
> On 25.04.2015 10:04, Kai Tietz wrote:
>> 2015-04-25 6:41 GMT+02:00 LRN wrote:
>>> On 24.04.2015 3:00, LRN wrote:
We have the prototype in the header (guarded as Vista-or-later), but no
stub in
the import library. I don't know how to fix that (.def f
On 25.04.2015 10:04, Kai Tietz wrote:
> 2015-04-25 6:41 GMT+02:00 LRN wrote:
>> On 24.04.2015 3:00, LRN wrote:
>>> We have the prototype in the header (guarded as Vista-or-later), but no
>>> stub in
>>> the import library. I don't know how to fix that (.def files for implibs
>>> seem
>>> to be sp
On 07.02.2015 2:55, Norbert Pfeiler wrote:
> Hello,
> it seems to be an issue that the 32 bit crt ships with a glut import
> library which is an ambigious match to freeglut for cmake.
>
> The package mingw-w64-i686-crt-git ships with
> /mingw32/i686-w64-mingw32/lib/libglut32.a and
> /mingw32/i686-
On 26.01.2015 4:49, Norbert Pfeiler wrote:
> Hello,
> it seems to be an issue that the 32 bit crt ships with a glut import
> library which is an ambigious match to freeglut for cmake.
>
> The package mingw-w64-i686-crt-git ships with
> /mingw32/i686-w64-mingw32/lib/libglut32.a and
> /mingw32/i686-
On 22.01.2015 5:01, Dongsheng Song wrote:
> On Thu, Jan 22, 2015 at 1:03 AM, Alexey Pavlov wrote:
>>
>> Current "mkstemp" implementation call "_sopen_s" that is not present in
>> WinXP msvcrt.dll. So this break supporting WinXP.
>>
>
> I have no WinXP now, but '_sopen_s' in the msvcrt.def file:
>
> pavel wrote:
>
>> On Tue, 2010-05-04 at 13:26 +0200, pavel wrote:
>>>
>>> why the latest release links the programs with the
>>> "libgcc_s_sjsj-1.dll"? Is it possible to avoid that?
>>
>> I have figured this out already.
>
> Just for the record, how do you avoid this?
You use --enable-static
