Re: [Gnash-dev] Diff for libbase under MSVC++ WIn32

[Tonko Juricic]

I can try run autoconf (with obligatory M4) from
http://gnuwin32.sourceforge.net/packages.html
and then try adapt it for MSVC.

However, these binaries were built with MingW and I am not sure how
will that work with MSVC. IOW, I am not aware of any genuine
MSVC-compatible version of autoconf. Could be it is just a few headers
difference but I can't tell you for sure right now.

Also I was trying to address <unistd.h> and <sys/time> issue (and
there will be few more, probably). In quite a few cases these are
included in headers or even cpp files where "gnashconfig.h" is either
not included or is included conditionally. This forces me to add
ifdefs for MSVC that were not required for MinGW since it had
Win32-compatible version of these headers. I would rather move
unistd.h and <sys/time> conditional inclusion to gnashconfig.h but
then non-Windows code that doesn't include gnashconfig.h or doesn't
include unistd.h inside gnashconfig.h would be broken unless modified.

I am not sure what would be the best course of action and I tended to
treat gnashconfig.h for MSVC differently since all typical header and
function existence conditionals are not particularly useful for a pure
MSVC compilation. Since you can't produce them automatically, may as
well manually create a simplified version of the file - that was my
line of thinking.

On Thu, Nov 20, 2008 at 12:27 PM, Dossy Shiobara <address@hidden> wrote:
> Benjamin Wolsey wrote:
>> Isn't it possible to provide a
>> gnashconfig.h for msvc++? That would be a better solution from my point
>> of view.
>
> If we want to skip autoconf on Win32/MSVC, then yeah, I'd rather see a
> gnashconfig.h.msvc created, and then the pre-build config step would
> look something like:
>
>  copy gnashconfig.h.msvc gnashconfig.h
>
> --
> Dossy Shiobara              | address@hidden | http://dossy.org/
> Panoptic Computer Network   | http://panoptic.com/
>  "He realized the fastest way to change is to laugh at your own
>    folly -- then you can let go and quickly move on." (p. 70)
>