Already having the code to point to different functions on different
platforms and having the routines for various OSes it would be a shame
to support only POSIX.
How can we call libcdio platform independent if we support only POSIX
systems and what is the point of this library?
If we support only POSIX we can get rid of a lot of abstraction that was
already done.
Also Pete Batard spent a lot of his time getting libcdio to compile on
MSVC.
I am a convinced Linux user but imho as long as the projects using
libcdio like VLC are released for other systems we should try to do so,
too. The demand is there.
What we do need are people to test and maintain the releases for the
different systems. We can talk a lot about what to do or not to do but
without individual care it will not work out. Every release has to be
tested on every system we claim to support and should at least have all
the major features.
This does not have to be the case with git. If a POSIX developer submits
a patch imho it would be wrong asking him to test it with MSVC. I would
prefer to have somebody make sure MSVC works before a release rather
than testing every patch for MSVC compatibility.
We should encourage people to use the release tarballs. Most of the time
the git version had some more features but was not as stable and once it
became stable there was a release.
If the git version lacks some files MSVC needs, there should at least be
a guide for MSVC developers of how to generate them.
Let me conclude.
Yes for MSVC support (and other systems if there are people caring)
No for requiring MSVC compatibility in git but providing a guide
Regards
Leon
Am 18.03.2012 05:23, schrieb Rocky Bernstein:
There has been a lot (possibly too much) back and forth regarding support
for development on native Microsoft C compilers. In the past, there has
been interest in supporting development on Sun's native C compiler.
I realize the crowd here isn't likely to be avid Microsoft C developers,
but if you could put aside individual biases in the following broader
question I would appreciate it.
To what extent should libcdio try to support non-POSIX systems?
Microsoft Windows is probably the biggest avowedly non-POSIX (or
POSIX-hostile) system. But if you want examples of others: BEOS, Amiga,
VMS, OS/2, Plan9 (which is probably pretty POSIX).
