Thread View: comp.os.ms-windows.programmer.misc
3 messages
3 total messages
Started by Aaron C. Coday
Tue, 19 Mar 1996 15:41
Solaris code -> Windows NT?
Author: Aaron C. Coday
Date: Tue, 19 Mar 1996 15:41
Date: Tue, 19 Mar 1996 15:41
22 lines
1234 bytes
1234 bytes
Hello , Has anyone out there ported signficant amount of code from Solaris to Windows NT? If so, I would like to hear about it. Particularly any pitfalls, etc. I'm facing possibly porting a large project to Windows NT. As I understand it, it should be easier than trying to port to Windows 3.x, because Solaris and NT both use flat memory models. Any traps? -Aaron -- -------------------------------------------------- Aaron Coday Aaron_Coday@ccm.fm.intel.com Intel Corp. 1900 Prairie City Rd. All opinions expressed are FM3-138 my own views and do not Folsom, CA 95630 represent official Intel (916)356-3114 views in any manner. --------------------------------------------------
Re: Solaris code -> Windows NT?
Author: Chris Marriott
Date: Mon, 25 Mar 1996 19:04
Date: Mon, 25 Mar 1996 19:04
31 lines
2084 bytes
2084 bytes
In article <314ED5A2.2CF7@ccm.fm.intel.com>, "Aaron C. Coday"
<aaron_coday@ccm.fm.intel.com> writes
>Has anyone out there ported signficant amount of code from Solaris
>to Windows NT? If so, I would like to hear about it. Particularly
>any pitfalls, etc.
>
>I'm facing possibly porting a large project to Windows NT. As I
>understand it, it should be easier than trying to port to
>Windows 3.x, because Solaris and NT both use flat memory models.
In my "day job" I work on and maintain the NT version of a large
distributed application development toolkit which runs on a dozen
different varieties of Unix, as well as NT, OS/2, VMS etc. I did the
original port from Unix to NT of this product.
It really is pretty easy; Unix code written with portability in mind (as
our code is) ports pretty much straight off to NT. For networking, NT's
socket library is virtually the same as the standard Unix Berkeley
sockets library, and almost all Unix system calls have 1:1 equivalents
in NT.
You really shouldn't have too many problems.
Chris
--------------------------------------------------------------------------
Chris Marriott, Warrington, UK | Author of SkyMap v3 award-winning
chris@chrism.demon.co.uk | shareware Win31/Win95 planetarium.
For full info, see http://www.execpc.com/~skymap
Author member of Association of Shareware Professionals (ASP)
--------------------------------------------------------------------------
Re: Solaris code -> Windows NT?
Author: Edmond
Date: Wed, 27 Mar 1996 03:25
Date: Wed, 27 Mar 1996 03:25
23 lines
1385 bytes
1385 bytes
Chris Marriott <chris@chrism.demon.co.uk> wrote: >It really is pretty easy; Unix code written with portability in mind (as >our code is) ports pretty much straight off to NT. For networking, NT's >socket library is virtually the same as the standard Unix Berkeley >sockets library, and almost all Unix system calls have 1:1 equivalents >in NT. > >You really shouldn't have too many problems. > >Chris I believe there is a POSIX.2 implementation available for Windows NT now also. X-open should be coming this spring. This should make things much easier. ----------------------------------------------------------------------- Edmond Underwood E-mail: underwoe@Colorado.Edu Bench32 1.10 final beta for Windows NT Bench32 1.07b for Windows 95 http://www.rmii.com/~underwoe/bench32.html.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads