"Suhaib Siddiqi" <[EMAIL PROTECTED]> wrote:
>1) U/WIN lacks GNU tools support therefore I consider it to a very user
>unfriendly and pain in the neck kind of tool.
Could you be more precise? I think if you have VC++ installed, there
is no need to install egcs and things may work better (better integration
into Windoze). The problem with autoconf configure not knowing about the
host type (you have to specify it manually) and libtool not working is
probably more on the autoconf side than is the fault of u/win.
>To most of the Linux code to U/WIN, you may end up spending several hours
>fideling with configure scripts.
That's something I probably wouldn't do anyways.
>2) You U/WIN messed up twice my NT permissions. I sent the bugs
>to Nilendu Pal and David Korn. David answer was, it must be windows
>messing up Windows permissions, because he never had this problems...
>not a porofessional answer. I hate those kind of answers, "It works OK
>on my system, so you there is no problem with my software."
Hmm... are these issues still problems with version 2.1?
I kindof like U/WIN so far, now it's only missing a Motif port (an
inexpensive or free one of course, since I use the Windows machine in
question only for non-professional stuff in my free time; I cannot
(attempt to) build OpenMotif on it for obvious license reasons either).
I mean, it shouldn't be too hard to port Lesstif to it, considering
that other X programs have been built aswell (I'll see if the DLL
issue with Xmu etc. will bite me). After one somehow kicked the
configure and libtool stuff through successfully I'd imagine that
actually compiling the stuff wouldn't be too much of an issue anymore,
would it?
mkb
