answersLogoWhite

0

Without getting into too much detail, it's largely a choice made by developers of the system whether or not providing a POSIX-compliant or at least POSIX-compatible system is worth the effort.

The aim of POSIX is not to be a standard defining operating systems themselves so much as standard for a suitable environment for source compatibility between different operating systems, primarily those of a Unix-compliant or Unix-like design. I believe full POSIX compliance is a requirement of the Single Unix Specification in turn, the SUS being a standard that actually DOES define what an operating system should be (In this case, to be considered a real UNIX system. Needless to say Windows is nowhere in the neighborhood of SUS compliance.).

The idea behind POSIX is to make it much easier for Unix/Unix-like software developers to write software and have it available for those who provide selections of software for any given Unix platform. Program written for POSIX OS A can be built for POSIX OS B with little or no changes to the source code of the program, usually the only changes needed are bits closer to the metal or usage of libraries not concerned with POSIX compliance.

POSIX does not concern itself or define any standard for binary compatibility. This is not just a matter of scope but the fact that such an application of the standard would only be useful on OS-to-OS ports of a program being made on the same system architectute, which would make POSIX less useful for Unix systems, which are frequently deployed in mixed-architecture environments.

Windows has a POSIX layer available as a download, but generally it's a limited, only halfway-compliant POSIX system. Windows itself is not designed in a way that is generally POSIX-compatible, since it's software architecture is a fundamentally very different thing from Unix. For most Windows users and developers: POSIX compliance is of very little practical use, as Windows' design still requires some very POSIX-unfriendly additions to source code to build correctly on Windows. For Windows to become a POSIX system would require Windows itself to be completely remade in ways that breaks all backwards compatibility with previous versions of Windows, something most users would not like. When open source software is ported to Windows, one generally uses MinGW or tools like cmake that provide build scripts/files for POSIX and non-POSIX systems alike.

User Avatar

Wiki User

12y ago

What else can I help you with?

Trending Questions
What is the name of the Seagate utility that can be used to test a hard drive and diagnose a hard drive problem? What is a teaching application in cognitive application? What education is required to become a game designer? How do you watch movies on iPod Nano? How has the development of military technology affected other technological fields? A file that contains the styles in a presentation including the type and size of bullets and fonts placeholder sizes and positons background design and fill color schemes? What is the maximum directly addressable memory capacity of 64 bit microprocessor having 64-bit instruction composedof two fields the first 2 bytes for op code and the remaining for the operand addres? What Smart Art graphic layout shows how parts relate to a whole? Does your mac book have a built in webcam that can be used for Skye? Dell loptop 110L error code a03 bios error? How do you restore factory settings of Lenovo ideapad s10? How do you convert liters to fl oz? Where can you find the scanner frequency numbers for free? How does one become a network administrator on their computer? If an administrator is concerned about security on a system which file system is appropriate? Which motherboard seems to provide the best possibility for expansion? What will happen if you use another person's profile on speech recognition? Can a Dell laptop track a specific PC? Is there a refresh f5 button on computers for hdmi cables? How many utility software?