X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <494125C0.70007@sbcglobal.net>
Date: Thu, 11 Dec 2008 06:37:52 -0800
From: Tim Prince <TimothyPrince AT sbcglobal DOT net>
Reply-To: tprince AT computer DOT org
User-Agent: Thunderbird 2.0.0.18 (X11/20081112)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: FW: how do i port applications from linux environment to windows  vc++
References: <7D453D0504B6A2429F98F4D72CBEDE4941B3571A AT nwd2exm5 DOT ad DOT analog DOT com>
In-Reply-To: <7D453D0504B6A2429F98F4D72CBEDE4941B3571A@nwd2exm5.ad.analog.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Rajagopal, Prasanth wrote:

> I am not sure if this is the right forum to ask this question, but how
> do I port applications from Linux environment to windows vc++?
Not the right forum, if you're thinking of adding non-portable stuff, or
you depend on stuff not supported by VC.
> Assume I have only the C source codes, which do not use any system calls
> at all. But what about the header files? And Compiler difference?
> What all should I take care? 
Already outside the scope of this forum.  You can run CL /?  I'll mention
that VC doesn't support std=c99; some of the features are available in
C++, of course.  Nor does VC support auto-vectorization; surely you knew
that.  Options aren't entirely consistent between x86 and x64.
>  
> I have an application that I compiled and executed with cygwin and now I
> want to move that to VC++.  
I open a cmd window which is set up in accordance with vcvarsxx.bat, and
then run my \cygwin\cygwin  .bat script, so as to have bash and make
available.  I make a separate version of my Makefile with VC9 options.
You may call it cheating, but attempts to use ancient versions of NM are
to be avoided; gnu make is viable with VC in both cygwin and mingw
versions.  GUI issues are well outside the scope of this list.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/