Wireshark-dev: Re: [Wireshark-dev] Now problems packaging ...
From: Graham Bloice <[email protected]>
Date: Sun, 1 Feb 2015 20:12:02 +0000
On 1 February 2015 at 14:38, Richard Sharpe <[email protected]> wrote:
On Sun, Feb 1, 2015 at 2:37 AM, Graham Bloice
<[email protected]> wrote:
> On 31 January 2015 at 22:55, Richard Sharpe <[email protected]>
> wrote:
>>
>> On Sat, Jan 31, 2015 at 2:39 PM, Richard Sharpe
>> <[email protected]> wrote:
>> > Hi folks,
>> >
>> > So, my build completed OK. However, when I attempted the packaging step
>> > I got:
>> >
>> > ----------------------------------
>> > Processing config: c:\Program Files (x86)\NSIS\nsisconf.nsh
>> > Processing script file: "wireshark.nsi" (ACP)
>> > File:
>> > "c:\Users\rjsharpe\Wireshark\Wireshark-win64-libs\vcredist_x64.exe" -> no
>> > files found.
>> > Usage: File [/nonfatal] [/a] ([/r] [/x filespec [...]] filespec [...] |
>> >    /_oname_=outfile one_file_only)
>> > Error in script "wireshark.nsi" on line 349 -- aborting creation process
>> > NMAKE : fatal error U1077: '"\Program Files (x86)\NSIS\makensis.exe"' :
>> > return c
>> > ode '0x1'
>> > Stop.
>> > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
>> > Studio 12.0
>> > \VC\BIN\amd64\nmake.exe"' : return code '0x2'
>> > Stop.
>> > --------------------------------
>> >
>> > Any hints here?
>>
>> A quick application of the vcredist_x64 tonic seems to have fixed this
>> problem.
>>
>> The doc needs another update.
>>
>
> Which VS edition are you using?

VS2013 ...


Odd, is that VS2013 Express, VS2013 Community Edition or some other version?  I believe all versions except the Express, which has now been withdrawn by MS in favour of the Community edition, include the vcredist files so no download is needed.

What flavour of VS2013, and what do you have in "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\redist\1033"?

There is already a note in the docs (Sect 4.6.1) about other VS variants that discusses the vcredist files for VS2010 Express, but as there is no conceivable reason I can think of to not use VS2013 CE, then it's all rather historical.

--
Graham Bloice