DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=g/JqaoKLrJ3ddVNBMPP9kIRDp/ofj3L0GbTS3Ml809X
	Ou3MRj0jOZHhr0ZR8nigVfaIuA0VMKXMVQ/EKJANqGngijAcDXU2yeihKLl5EuXv
	TX7hWuUbj1vexzFOlr+3z3Q0qFo0OmMtZbvwC2vU4EFO71l7JjvjHbrmjMTvPqdE
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <53BF16CE.4070406@codespunk.com>
Date: Thu, 10 Jul 2014 18:42:22 -0400
From: "Matt D." <matt@codespunk.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: using make without cygwin terminal
References: <CACr0xSMvizCYiyFW14gfTAoOTajUYue+d+mqFBpq8HQGMUAEug@mail.gmail.com> <CAAeCd-PoUK1ZyjY9VYwFOt58McOdXn4buVMz1HykaW9tZmKJcg@mail.gmail.com>
In-Reply-To: <CAAeCd-PoUK1ZyjY9VYwFOt58McOdXn4buVMz1HykaW9tZmKJcg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Rob,

You need to setup your environment paths to include both the compiler's 
include and libs directories as well as the targeted platform sdk, if 
you're using one.

I use a custom tool chain with Cygwin/GNU Make in my build system with 
support for every version of Visual Studio, including 6.

Here is an example of the required paths:

Includes:
vs6/vc98/include
vs6/vc98/mfc/include
vs6/vc98/atl/include

Libs:
vs6/vc98/lib
vs6/vc98/mfc/lib

Visual Studio 6 is compatible with the Windows platform SDK up to 
"Windows Server 2003 R2 Platform SDK", but you shouldn't need it.

Your shell environment will need to be setup for both the compiler 
(cl.exe) and the linker (link.exe). See here:

http://msdn.microsoft.com/en-us/library/aa236630(v=vs.60).aspx
http://msdn.microsoft.com/en-us/library/aa270757(v=vs.60).aspx


Matt D.

On 7/10/2014 6:14 PM, Robert Pendell wrote:
> On Thu, Jul 10, 2014 at 12:46 PM, Okan Erat wrote:
>> Dear Cygwin users,
>>
>> I am trying to compile a project using VS6 compiler and makefiles
>> generated by imake.
>> When i run make from cygwin terminal it compiles everything without any problem.
>> However if i run make from windows terminal (c:/cygwin/bin is already in Path)
>> VS6 complains about various problems.
>>   such as:
>>
>> winbase.h(1011) : error C2733: second C linkage of overloaded function
>> 'InterlockedIncrement' not allowed
>>
>> mswsock.h(69) : error C2065: 'SOCKET' : undeclared identifier
>>
>> winsock2.h(85) : error C2378: 'SOCKET' : redefinition; symbol cannot
>> be overloaded with a typedef
>>
>> Why make works with cygwin terminal but not with windows terminal.
>>
>> Thanks for your answers
>
> Those errors are not coming from cygwin make.  That's coming from VS6
> make.  Cygwin make doesn't have errors formatted that way.
>
> With that in mind Visual Studio is a Microsoft product and not really
> supported here.
>
> Robert Pendell
> A perfect world is one of chaos.
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>
>
>

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