public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* using make without cygwin terminal
@ 2014-07-10 16:46 Okan Erat
  2014-07-10 22:14 ` Robert Pendell
  0 siblings, 1 reply; 4+ messages in thread
From: Okan Erat @ 2014-07-10 16:46 UTC (permalink / raw)
  To: cygwin

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

--
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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: using make without cygwin terminal
  2014-07-10 16:46 using make without cygwin terminal Okan Erat
@ 2014-07-10 22:14 ` Robert Pendell
  2014-07-10 22:42   ` Matt D.
  2014-07-11  1:00   ` Warren Young
  0 siblings, 2 replies; 4+ messages in thread
From: Robert Pendell @ 2014-07-10 22:14 UTC (permalink / raw)
  To: cygwin

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: using make without cygwin terminal
  2014-07-10 22:14 ` Robert Pendell
@ 2014-07-10 22:42   ` Matt D.
  2014-07-11  1:00   ` Warren Young
  1 sibling, 0 replies; 4+ messages in thread
From: Matt D. @ 2014-07-10 22:42 UTC (permalink / raw)
  To: cygwin

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: using make without cygwin terminal
  2014-07-10 22:14 ` Robert Pendell
  2014-07-10 22:42   ` Matt D.
@ 2014-07-11  1:00   ` Warren Young
  1 sibling, 0 replies; 4+ messages in thread
From: Warren Young @ 2014-07-11  1:00 UTC (permalink / raw)
  To: Cygwin-L

On 7/10/2014 16:14, Robert Pendell wrote:
> On Thu, Jul 10, 2014 at 12:46 PM, Okan Erat wrote:
>> Dear Cygwin users,
>>
>> winbase.h(1011) : error C2733: second C linkage of overloaded function
>> 'InterlockedIncrement' not allowed
>
> Those errors are not coming from cygwin make.  That's coming from VS6
> make.  Cygwin make doesn't have errors formatted that way.

Nope.  Microsoft make is called "nmake.exe", not "make.exe".  The errors 
are coming from cl, the Visual C++ compiler.

The only reason this isn't off-topic is that the same makefile is being 
run by Cygwin make in both cases, according to the OP.  He may be wrong, 
but I think it's got to be something a bit stranger than a simple typo 
in the command.

> With that in mind Visual Studio is a Microsoft product and not really
> supported here.

It's on-topic if the problem is happening via Cygwin make in both cases. 
  The OP should go the extra mile to make sure that that is in fact the 
case.

--
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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-07-11  1:00 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-07-10 16:46 using make without cygwin terminal Okan Erat
2014-07-10 22:14 ` Robert Pendell
2014-07-10 22:42   ` Matt D.
2014-07-11  1:00   ` Warren Young

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).