imacarthur wrote:
> I acknowledge that we have differing views on this, but I do not believe
> that "cygwin -mno-cygwin" is actually the same thing as mingw.
>
> In particular, I think that the -mno-cygwin option mainly turns off the
> use of the "posix emulation" features of cygwin, but I do not think it
> stops the use of cygwin's own built in libc etc.
Well, I really don't *know*, but the cygwin people seem to say that
(that this is a mingw build, essentially).
I'm reading the cygwin mailing list, and there are some facts(?) that
I read more than once:
(1) gcc -mno-cygwin does invoke the mingw compiler suite
(2) the resulting executables don't link to cygwin1.dll
(3) sometimes people even get answers that they are OT in the cygwin
mailing list if they ask questions regarding -mno-cygwin.
However, I don't know if there are runtime libs that the compiler links
with, so that there is a possibility that gcc -mno-cygwin would link in
some special (cygwin) object files.
> (IIRC, at one point in the past, cygwin's libc etc were derived from
> newlib... they may have moved to something else since, of course.)
It's still newlib, and this is used to build cygwin1.dll.
> The mingw build provides no libc etc., it simply wraps the MS runtime
> already on the system: and that, I suspect, is why we see differing
> results with this test.
Well, that's what I thought that my cygwin "gcc -mno-cygwin" build
would do, too ;-)
[...]
>> #ifdef _WIN32
>> extern "C" int fl_snprintf(char *, size_t, const char *, ...);
>> #define snprintf fl_snprintf
>> #endif /*MICROSOFT*/
>>
>> instead of trying to use _snprintf_s, because we do already have
>> this in src/vsnprintf.c :-)
>
>
> Oh! Now that might be a good way out of this...
[...]
> I'll need to try this in a mingw build too - time permitting! - but this
> looks like a solution that will work in a general way across all the
> win32 variants. Wonder if it flies for Greg with MS VS, too?
Yes, this would be very interesting...
Albrecht
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
