From: Mumit Khan <khan@nanotech.wisc.EDU>
To: David Most <dmost@ascend.com>
Cc: cygwin users <cygwin@sourceware.cygnus.com>
Subject: Re: Using Microsoft Visual C
Date: Thu, 30 Sep 1999 23:42:00 -0000 [thread overview]
Message-ID: <199909231810.NAA23453@mercury.xraylith.wisc.edu> (raw)
Message-ID: <19990930234200.YTaKko8Yw3f0GpbRmc2CcZVD5lWHdifAV6s4AOYsOQk@z> (raw)
In-Reply-To: <4.1.19990923091908.00aef1e0@basset.eng.ascend.com>
David Most <dmost@ascend.com> 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 <g>)?
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
next prev parent reply other threads:[~1999-09-30 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-23 6:17 Getting simple STL program to compile Earnie Boyd
1999-09-23 6:44 ` Using Microsoft Visual C David Most
1999-09-23 11:12 ` Mumit Khan [this message]
1999-09-30 23:42 ` Mumit Khan
1999-09-30 23:42 ` David Most
1999-09-30 23:42 ` Getting simple STL program to compile Earnie Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199909231810.NAA23453@mercury.xraylith.wisc.edu \
--to=khan@nanotech.wisc.edu \
--cc=cygwin@sourceware.cygnus.com \
--cc=dmost@ascend.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).