From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mumit Khan To: David Most Cc: cygwin users Subject: Re: Using Microsoft Visual C Date: Thu, 23 Sep 1999 11:12:00 -0000 Message-id: <199909231810.NAA23453@mercury.xraylith.wisc.edu> References: <4.1.19990923091908.00aef1e0@basset.eng.ascend.com> X-SW-Source: 1999-09/msg00353.html David Most writes: > I'm working on a project which is a mix of UNIX and Windows. A large > portion of the base-code is ANSI/UNIX, with the edges (GUI & audio i/o) in > Win32. > > I would like to get migrate the project from cygwin/gcc to MSVC. Ideally, > I'd simply point the compiler at the cygwin unix headers and link to the > cygwin DLL. Has anyone attempted this with success? Do you have any tips > for me? Am I on the right track (not referring to the migration towards > windows )? You may be able to do this, but may run into problems with the linking to libcygwin.a, which is not quite compatible to what MSVC linker expects. In the future, when GNU as/ld is completely PE compatible, it should work in theory. If you want to experiment, I suggest rebuilding the import library using LIB.EXE (or whatever MSVC uses), add back the static archive objects into the import library and see how things go. I doubt if anyone's tried this yet, so it's up to you. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mumit Khan To: David Most Cc: cygwin users Subject: Re: Using Microsoft Visual C Date: Thu, 30 Sep 1999 23:42:00 -0000 Message-ID: <199909231810.NAA23453@mercury.xraylith.wisc.edu> References: <4.1.19990923091908.00aef1e0@basset.eng.ascend.com> X-SW-Source: 1999-09n/msg00353.html Message-ID: <19990930234200.YTaKko8Yw3f0GpbRmc2CcZVD5lWHdifAV6s4AOYsOQk@z> David Most writes: > I'm working on a project which is a mix of UNIX and Windows. A large > portion of the base-code is ANSI/UNIX, with the edges (GUI & audio i/o) in > Win32. > > I would like to get migrate the project from cygwin/gcc to MSVC. Ideally, > I'd simply point the compiler at the cygwin unix headers and link to the > cygwin DLL. Has anyone attempted this with success? Do you have any tips > for me? Am I on the right track (not referring to the migration towards > windows )? You may be able to do this, but may run into problems with the linking to libcygwin.a, which is not quite compatible to what MSVC linker expects. In the future, when GNU as/ld is completely PE compatible, it should work in theory. If you want to experiment, I suggest rebuilding the import library using LIB.EXE (or whatever MSVC uses), add back the static archive objects into the import library and see how things go. I doubt if anyone's tried this yet, so it's up to you. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com