Re: [Wireshark-dev] Win7 - 64 bit build
Alex Lindberg wrote: One additional item. When building an NSIS install package on a Win7 64 bit system, the NSIS installs to C:\Program Files (x86)\NSIS. In config.nmake, the makensis.exe files uses C:\Program Files, thus failing. I did the following: Added: PROGRAM_FILES_NSIS=%%ProgramFiles(x86)%% Changed: MAKENSIS=$(PROGRAM_FILES)\NSIS\makensis.exe To: MAKENSIS=$(PROGRAM_FILES_NSIS)\NSIS\makensis.exe Worked like a charm. I would guess that there are more elegant solutions to the problem that would detect the path and make the correct choice. I will leave that to folks smarter than me. I have made a patch for the Developer Guide to better describe how to build either 32-bit or 64-bit versions of the code and also made a note about this issue. I think you must have installed the 64-bit version of NSIS rather than the 32-bit version 2.46 which is linked to in the instructions. Can you please check that? The patch is attached to bug 8386 (see https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8386 ) which also describes the changes made. Ed ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Win7 - 64 bit build
On 31 January 2013 00:18, Ed Beroset bero...@mindspring.com wrote: Alex Lindberg wrote: I was having issues compiling a x64 build of Wireshark on a Win7x64 bit PC. I followed the instructions to the letter as referenced in the Win build page: http://www.wireshark.org/docs/**wsdg_html_chunked/** ChSetupWin32.htmlhttp://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html All to no avail. After reinstalling several times and googling for most of the day, the answer was found. The referenced sugested setup batch file to build x64 Wireshark is: @echo off echo Adding things to the path... set PATH=%PATH%;. set PATH=%PATH%;c:\cygwin\bin echo Setting up Visual Studio environment... call c:\Program Files\Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat amd64 title Command Prompt (VC++ 2010) The issue was that the vcvars32.bat amd64 branch is broken. The script is looking for files that don't exist. To fix this the line 'call c:\windows... line should now read: call c:\Program Files\Microsoft SDKs\Windows\v7.1\BIn\SetEnv.**cmd /x64 The /x64 can be changed to set any number of different compile options. Thanks for reporting back. I have been intending to redo the build instructions for a while and this gives me both the confirmation that the existing instructions really need revision and that the edits that I have in mind will work. Now all I need is to actually get around to doing the work! :) Thanks! Ed Note that the extra options to SetEnv could be important, the default is to build a debug version (/Debug), targeted at Win7 (/WIN7). Read the first part of SetEnv to get all the options info. Graham ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Win7 - 64 bit build
One additional item. When building an NSIS install package on a Win7 64 bit system, the NSIS installs to C:\Program Files (x86)\NSIS. In config.nmake, the makensis.exe files uses C:\Program Files, thus failing. I did the following: Added: PROGRAM_FILES_NSIS=%%ProgramFiles(x86)%% Changed: MAKENSIS=$(PROGRAM_FILES)\NSIS\makensis.exe To: MAKENSIS=$(PROGRAM_FILES_NSIS)\NSIS\makensis.exe Worked like a charm. I would guess that there are more elegant solutions to the problem that would detect the path and make the correct choice. I will leave that to folks smarter than me. From: Graham Bloice graham.blo...@trihedral.com To: Developer support list for Wireshark wireshark-dev@wireshark.org Sent: Thursday, January 31, 2013 3:50 AM Subject: Re: [Wireshark-dev] Win7 - 64 bit build On 31 January 2013 00:18, Ed Beroset bero...@mindspring.com wrote: Alex Lindberg wrote: I was having issues compiling a x64 build of Wireshark on a Win7x64 bit PC. I followed the instructions to the letter as referenced in the Win build page: http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html All to no avail. After reinstalling several times and googling for most of the day, the answer was found. The referenced sugested setup batch file to build x64 Wireshark is: @echo off echo Adding things to the path... set PATH=%PATH%;. set PATH=%PATH%;c:\cygwin\bin echo Setting up Visual Studio environment... call c:\Program Files\Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat amd64 title Command Prompt (VC++ 2010) The issue was that the vcvars32.bat amd64 branch is broken. The script is looking for files that don't exist. To fix this the line 'call c:\windows... line should now read: call c:\Program Files\Microsoft SDKs\Windows\v7.1\BIn\SetEnv.cmd /x64 The /x64 can be changed to set any number of different compile options. Thanks for reporting back. I have been intending to redo the build instructions for a while and this gives me both the confirmation that the existing instructions really need revision and that the edits that I have in mind will work. Now all I need is to actually get around to doing the work! :) Thanks! Ed Note that the extra options to SetEnv could be important, the default is to build a debug version (/Debug), targeted at Win7 (/WIN7). Read the first part of SetEnv to get all the options info. Graham ___ Sent via: Wireshark-dev mailing list wireshark-dev@wireshark.org Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Win7 - 64 bit build
I was having issues compiling a x64 build of Wireshark on a Win7x64 bit PC. I followed the instructions to the letter as referenced in the Win build page: http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html All to no avail. After reinstalling several times and googling for most of the day, the answer was found. The referenced sugested setup batch file to build x64 Wireshark is: @echo off echo Adding things to the path... set PATH=%PATH%;. set PATH=%PATH%;c:\cygwin\bin echo Setting up Visual Studio environment... call c:\Program Files\Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat amd64 title Command Prompt (VC++ 2010) The issue was that the vcvars32.bat amd64 branch is broken. The script is looking for files that don't exist. To fix this the line 'call c:\windows... line should now read: call c:\Program Files\Microsoft SDKs\Windows\v7.1\BIn\SetEnv.cmd /x64 The /x64 can be changed to set any number of different compile options. The file vcvars32.bat does exist and if you wish to compile 32 bit programs, all should be OK without this change. Thanks as always Alex Lindberg ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Win7 - 64 bit build
Alex Lindberg wrote: I was having issues compiling a x64 build of Wireshark on a Win7x64 bit PC. I followed the instructions to the letter as referenced in the Win build page: http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html All to no avail. After reinstalling several times and googling for most of the day, the answer was found. The referenced sugested setup batch file to build x64 Wireshark is: @echo off echo Adding things to the path... set PATH=%PATH%;. set PATH=%PATH%;c:\cygwin\bin echo Setting up Visual Studio environment... call c:\Program Files\Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat amd64 title Command Prompt (VC++ 2010) The issue was that the vcvars32.bat amd64 branch is broken. The script is looking for files that don't exist. To fix this the line 'call c:\windows... line should now read: call c:\Program Files\Microsoft SDKs\Windows\v7.1\BIn\SetEnv.cmd /x64 The /x64 can be changed to set any number of different compile options. Thanks for reporting back. I have been intending to redo the build instructions for a while and this gives me both the confirmation that the existing instructions really need revision and that the edits that I have in mind will work. Now all I need is to actually get around to doing the work! :) Thanks! Ed ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
