Re: Cross-compile to Windows NT
Hi... Well, my two cents: Java is lame. Slow, VERY slow, and lame. And abused. (I don't feel like having my web browser start lagging whenever I decide to look at some cool web page.) Alex On Fri, 17 Jul 1998, Stephen A. Witt wrote: Date: Fri, 17 Jul 1998 11:15:00 -0700 (PDT) From: Stephen A. Witt [EMAIL PROTECTED] To: Michael Laing [EMAIL PROTECTED] Cc: debian-user@lists.debian.org Subject: Re: Cross-compile to Windows NT Resent-Date: 17 Jul 1998 18:15:15 - Resent-From: debian-user@lists.debian.org Resent-cc: recipient list not shown: ; On Fri, 17 Jul 1998, Michael Laing wrote: I have a large utility program that I need to run under NT - is there a cross-compiler for this purpose? Thanks, Michael Yeah, 'gcc' (assuming it is written in C). Cross-compiling really means compiling a set of source files into an executable image that will run on a platform with a different CPU. This is very common in the embedded systems business (my work) in which you do software development on a Unix workstation, (less preferably) WinNT, or (even less perferably) some other box but the computer you are programming is something like a simgle board computer with a different CPU (like a Motorola 68040, 68360, 860, 68HC11, etc., etc.). The compiler running on the development workstation emits an executable image for the specific CPU that your target (the single board computer) is equiped with. You are really talking about using a 'native' compiler, one that emits an executable image for the same hardware architecture that it is being compiled on, and 'porting' your program to a different OS. So, you get your source files on the NT box and use your compiler/interpreter of choice (you haven't told us what language your program is written in) to cause that source to be converted into an executable image (this is the compiling and linking stages). We use the word 'port' to indicate that the software probably won't run unchanged on the new OS depending upon the extent to which OS facitilities are used and the difference between those facilities on the original OS vs. the new OS. I've written a LOT of Unix stuff (mostly for Sun OSs) and a LOT of embedded stuff (pSOS and VxWorks OSs) but not any Windows stuff (nor do I intend to, my employer willing), so I can't really give you any clue to what porting issues you might find going from Unix/Linux to NT. It really depends upon what your program does and its software architecture and what facilities from the OS it requires. If it requires very little from the OS, meaning that is uses mostly standard C library (again, assuming it is in C) stuff then it should be easy to port. Why not re-code it in Java, learn a cool language (if you aren't already Java fluent) and get the cross-platform stuff for free! -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Cross-compile to Windows NT
I'll assume the thing was written in C. Well. Don't expect it to work out of the box. But if it uses only the standard library, you may have luck with the mingw32 stuff at: http://www.d.shuttle.de/isil/cpd/mingw32-cpd.html I haven't tried it myself, as I usually compile from Win95. BUT I've used a similar tool suite (the only difference is that the compiler is egcs, and it is a native version, not a cross-compiler) with some success. If you need to port a full utility, you may have better luck with Cygnus' gnu-win32 tool suite. Take a look at http://www.cygnus.com/ They propose a rather complete POSIX environment under NT. Note that this ain't a cross-compiler; you need to compile from NT. There may be cross compilers using that tool suite for Linux lying around (I think I recall seeing a .deb for that at one point, but I don't know if it's still alive). -- Benoit Goudreault-Emond -- Reply to: [EMAIL PROTECTED] CoFounder, KMS Group. Student, B. CompEng, Concordia University. PGP public key fingerprint: 11 43 A9 04 7C 11 41 44 5F FC 69 B1 B6 0A ED 78 E-mail me to receive the actual public key. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Cross-compile to Windows NT
Benoit Goudreault-Emond wrote: I'll assume the thing was written in C. It is. Well. Don't expect it to work out of the box. But if it uses only the standard library, you may have luck with the mingw32 stuff at: http://www.d.shuttle.de/isil/cpd/mingw32-cpd.html This looks like what I wanted. Thanks. ml -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Cross-compile to Windows NT
I have a large utility program that I need to run under NT - is there a cross-compiler for this purpose? Thanks, Michael -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Cross-compile to Windows NT
On Fri, 17 Jul 1998, Michael Laing wrote: I have a large utility program that I need to run under NT - is there a cross-compiler for this purpose? Thanks, Michael Yeah, 'gcc' (assuming it is written in C). Cross-compiling really means compiling a set of source files into an executable image that will run on a platform with a different CPU. This is very common in the embedded systems business (my work) in which you do software development on a Unix workstation, (less preferably) WinNT, or (even less perferably) some other box but the computer you are programming is something like a simgle board computer with a different CPU (like a Motorola 68040, 68360, 860, 68HC11, etc., etc.). The compiler running on the development workstation emits an executable image for the specific CPU that your target (the single board computer) is equiped with. You are really talking about using a 'native' compiler, one that emits an executable image for the same hardware architecture that it is being compiled on, and 'porting' your program to a different OS. So, you get your source files on the NT box and use your compiler/interpreter of choice (you haven't told us what language your program is written in) to cause that source to be converted into an executable image (this is the compiling and linking stages). We use the word 'port' to indicate that the software probably won't run unchanged on the new OS depending upon the extent to which OS facitilities are used and the difference between those facilities on the original OS vs. the new OS. I've written a LOT of Unix stuff (mostly for Sun OSs) and a LOT of embedded stuff (pSOS and VxWorks OSs) but not any Windows stuff (nor do I intend to, my employer willing), so I can't really give you any clue to what porting issues you might find going from Unix/Linux to NT. It really depends upon what your program does and its software architecture and what facilities from the OS it requires. If it requires very little from the OS, meaning that is uses mostly standard C library (again, assuming it is in C) stuff then it should be easy to port. Why not re-code it in Java, learn a cool language (if you aren't already Java fluent) and get the cross-platform stuff for free! -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Cross-compile to Windows NT
You might be interested in the Cygnus GNU/win32 project. It's possible both setting up a cross linux-NT and building gcc+binutils for native NT operation. Check out http://www.cygnus.com/misc/gnu-win32/ -- GNUwin32 project home http://www.lexa.ru/sos/ -- Sergei Okhapkin's home page, read if you are interested in running `inetd' on your NT machine -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
