Wireshark-dev: Re: [Wireshark-dev] win32: nmake setup: can't find cl

From: "Cook, Timothy" <tcook@xxxxxxxxxxxxxxxxxx>
Date: Thu, 7 Sep 2006 14:35:53 -0400
Have you done the following:

Do you intend to build using MSVC & CYGWIN tools?
Was your Win32 build environment setup using the Developers Guide,
sections 2.3 & 4.6.2?

If you intended to use MSVC & CYGWIN tools, a command prompt [DOS
prompt] is the way to go!

Also ensure that you have run vcvars32.bat before calling nmake.  This
is normally in "Program Files\Microsoft Visual studio\VC98\bin".  This
sets lots of important paths and env vars for MSVC6.

I build using MSVC v6 & CYGWIN tools.


-Tim

> -----Original Message-----
> From: wireshark-dev-bounces@xxxxxxxxxxxxx 
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of 
> Jacques, Olivier (OpenCall Test Infra)
> Sent: Thursday, September 07, 2006 1:42 PM
> To: Developer support list for Wireshark
> Subject: [Wireshark-dev] win32: nmake setup: can't find cl
> 
> Hello,
>  
> I re-installed my PC and I'm trying to re-setup my wireshark 
> build environment. After a fresh svn checkout, a nmake -f 
> makefile.nmake distclean, I can't run "nmake -f 
> makefile.nmake setup": win32setup.sh complains about cl that 
> can't be found:
> ----------
> C:\transfer\ethereal\winbuild\ethereal>nmake -f makefile.nmake setup
>  
> Microsoft (R) Program Maintenance Utility   Version 6.00.8168.0
> Copyright (C) Microsoft Corp 1988-1998. All rights reserved.
>  
> Checking for required applications:
> 
> ERROR: Can't find cl. This is probably an optional cygwin 
> package not yet installed. Try to install it using cygwin's setup.exe!
>  
> NMAKE : fatal error U1077: 'bash' : return code '0x1'
> Stop.
>  
> ----------
> (side note: cl is not part of cygwin, maybe we should change 
> the message there).
> But cl is in the path (I ran vcvars32.bat).
> ----------
> C:\transfer\ethereal\winbuild\ethereal>cl
> Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for
> 80x86
> Copyright (C) Microsoft Corp 1984-1998. All rights reserved.
>  
> usage: cl [ option... ] filename... [ /link linkoption... ]
> ----------
> The issue seems to be that cygwin's "which" can't find "cl". 
> In win32setup.sh, this piece of code is checking the app:
> 		APP_PATH=`cygpath --unix $APP`
> 		if [ -x "$APP_PATH" -a ! -d "$APP_PATH" ] ; then
> 			APP_LOC="$APP_PATH"
> 		else
> 			APP_LOC=`which $APP_PATH 2> /dev/null`
> 		fi
> 
> Running which and cygpath, I get:
> ---------------------
> C:\transfer\ethereal\winbuild\ethereal>which cl
> cl: Command not found.
> 
> C:\transfer\ethereal\winbuild\ethereal>cygpath --unix cl cl
> ---------------------
> 
> Is there anyone that encountered the same problem? Any idea?
> 
> Thanks a lot,
> Olivier.
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
> 
> ______________________________________________________________
> _______________
> Scanned by IBM Email Security Management Services powered by 
> MessageLabs. For more information please visit 
> http://www.ers.ibm.com 
> ______________________________________________________________
> _______________
>