--- On Fri, 5/22/09, Philip Mason <[email protected]> wrote:
> From: Philip Mason <[email protected]>
> Subject: RE: [uwin-users] a wild guess on 'cc', 'pcc', MSVC, UNIXish OSes and
> Windows
> To: [email protected]
> Date: Friday, May 22, 2009, 2:13 PM
> Sergei,
>
> To emphasize what David Korn mentioned in his last post,
> UWIN is
> essentially the software to get the AST package (as well as
> other
> software) to run under Windows.
>
> Trying to get UWIN to run under Linux doesn't make a lot of
> sense. (At
> least it doesn't make a lot of sense to me ...)
>
> You need to clarify for yourself exactly what your goals
> are for using
> UWIN. If those goals do not include using AST, using
> the ATT
> build/package system or porting UNIX/Linux software to the
> Windows
> platform, then UWIN is not for you.
>
> If you want to try to have software that builds and runs
> under a similar
> environment on both Linux/UNIX *and* Windows, then you need
> to focus on
> AST for the UNIX/Linux side and AST/UWIN on the Windows
> side. Get
> *very* familiar with AST and the documentation for the
> build & package
> system used to build AST and UWIN and start from there.
>
> - - - Philip
>
>
The very first thing I did was reading the documentation and attempting
to build all I could under Linux.
Yes, I understand AST library is the key.
Several things failed to build under Linux, and to me the things that
failed look like general, not like Windows-specific.
I was busy trying UWIN under Windows, setting up environment, etc.
I'll hopefully return to Linux build and publish the failures.
Regards,
Sergei.
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
