Jay wrote:
David, thanks for replying.
realize: I am a potential user of both AST and/or UWin. I am not
sure which is which, and I don't think that is terrible. I added
myself to "all" the lists. I guess UWin is posix.dll and
pthreads.dll.AST is ksh and Graphvis and CDT.UWin is stuff
exclusively for Windows. AST is stuff on top of UWin and top of
"native Unix".
Hi Jay,
Quite correct. There are some subtleties. I've have liberally
cut in your message to focus on the nature of ast and uwin...
* Ast is a portable collection of various tools for any unix-like
environment, including the portability layer.
* Many of those tools (e.g. nawk) are from the original unix heritage,
although some have evolved on separate tracks (e.g., nmake).
* Windows never was a unix-like environment, which is the reason
why David had to build a separate additional compatibility layer
for windows. Some of the work involved was originally contracted
out to Wipro on a commercial basis. This is the reason why Uwin
was liberated later than the rest of ast.
* PRACTICAL REUSABLE UNIX SOFTWARE, Balachander Krishnamurthy, ed.,
puts ast in a historical perspective.
http://www.research.att.com/~gsf/publications/prus-1995-1.pdf
I'm not stupid..but I am a bit confused. The downloads are all
together. I understand UWin is a Unix portability layer akin to
Cygwin.
It's AST plus an additional posix layer, designed to run on top of
the standard[sic] Win32 api.
And AST is a bunch of "apps", like Graphviz, not a portability layer.
You'd build it on Cygwin or UWin, maybe either works similarly.
AST comes with its own portability layer, and its own build system,
based on nmake/iffe.
David and Glen can correct me where I'm wrong.
Cheers,
Henk
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
