sorry I made a mistake, to correct the problem I had to remove the ",0" after PRODUCTVERSION @RC_VERSION@ in "plugin.rc.in".
Can't remember how I got this file though, if I copied it from griphon plugin or if it got generated by python or whatever. On Tue, Sep 27, 2011 at 4:41 PM, Teto <[email protected]> wrote: > > I am impressed by the whole environment deployed for dev it's very > impressive, even documentation is top-notch. > > I noticed sthg wrong . In README.plugins, it is said to copy/paste all > files and modifying them accordingly. If I don't remove the trailing > ",$(MODULE_VERSION_EXTRA)" > in "moduleinfo.h" I get an error in windows 7 64 bits.: > energywise_udp.rc(5) : error RC2167 : unrecognized VERSIONINFO field; BEGIN > or > comma expected > > Is that a known problem ? > > Matt > > On Mon, Sep 26, 2011 at 3:56 PM, Teto <[email protected]> wrote: > > > > I could test your solution today. The poor PC took 4 hours to compile > > everything but it worked. Thanks a lot !! > > > > On Fri, Sep 23, 2011 at 12:43 PM, Anders Broman > > <[email protected]> wrote: > > > > > > Hi, > > > In config nmake change > > > > > > ##### Target platform ##### > > > # Only "win32" and "win64" are valid (for now). > > > # This can be defined in the system environment. > > > !IFNDEF WIRESHARK_TARGET_PLATFORM > > > WIRESHARK_TARGET_PLATFORM=win32 > > > !END > > > > > > And read http://wiki.wireshark.org/Development/Win64 > > > > > > Regards > > > Anders > > > > > > -----Original Message----- > > > From: [email protected] > > > [mailto:[email protected]] On Behalf Of Teto > > > Sent: den 23 september 2011 12:36 > > > To: [email protected] > > > Subject: [Wireshark-dev] Problem compiling SVN because of a mismatch > > > 32/64 bits ? > > > > > > Hi to all, > > > > > > I want to improve energywise support in wireshark, that's why I try to > > > compile wireshark on windows 7 64 bits. I've met various problems I list > > > here for future googlers: > > > > > > Makefile.nmake(10) : fatal error U1052: file 'win32.mak' not found => I > > > installed Windows SDK and that solved it NMAKE : fatal error U1077: 'sed' > > > : return code '0x1' => Don't put space " " in VERSION_EXTRA ! this should > > > be added to the superb developer guide: > > > http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html#id578236 > > > > > > Here is my current problem: i've launched a terminal throug cmd /V:ON to > > > enable "delayed variable expansion" as explained here > > > http://social.msdn.microsoft.com/Forums/en/windowssdk/thread/b8f02d5d-a52c-4fa2-8ff1-5b0a0cd60255. > > > then I call SetEnv.cmd in the windows SDK folder. > > > > > > Then I cd c:\wireshark and launch "nmake -f Makefile.nmake all". > > > Firstly I ran into this problem: > > > I"'ml': is not recognized as an internal or external command, operable > > > program or batch file" > > > so I went to C:\Program Files (x86)\Microsoft Visual Studio > > > 9.0\VC\bin\amd64 and renamed ml64.exe to ml.exe and here comes the > > > output: > > > > > > > > > ========= > > > ml -c -coff -Zi -DASMV -DASMINF contrib/masmx86\inffas32.asm Microsoft > > > (R) Macro Assembler (x64) Version 9.00.30729.01 Copyright (C) Microsoft > > > Corporation. All rights reserved. > > > > > > MASM : warning A4018:invalid command-line option : -coff > > > Assembling: contrib/masmx86\inffas32.asm > > > contrib/masmx86\inffas32.asm(64) : error A2008:syntax error : . > > > contrib/masmx86\inffas32.asm(65) : error A2008:syntax error : . > > > contrib/masmx86\inffas32.asm(68) : error A2008:syntax error : . > > > contrib/masmx86\inffas32.asm(167) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(168) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(169) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(170) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(171) : error A2008:syntax error : pushfd > > > contrib/masmx86\inffas32.asm(279) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(280) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(281) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(282) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(283) : error A2008:syntax error : pushfd > > > contrib/masmx86\inffas32.asm(290) : error A2008:syntax error : popfd > > > contrib/masmx86\inffas32.asm(291) : error A2008:syntax error : pushfd > > > contrib/masmx86\inffas32.asm(292) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(318) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(319) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(320) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(321) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(1075) : error A2008:syntax error : popfd > > > contrib/masmx86\inffas32.asm(1076) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(1077) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(1078) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(1079) : error A2070:invalid instruction > > > operands > > > contrib/masmx86\inffas32.asm(710) : error A2022:instruction operands must > > > be the same size > > > contrib/masmx86\inffas32.asm(751) : error A2022:instruction operands must > > > be the same size > > > contrib/masmx86\inffas32.asm(810) : error A2022:instruction operands must > > > be the same size > > > contrib/masmx86\inffas32.asm(823) : error A2022:instruction operands must > > > be the same size ========= > > > > > > It looks to me that I am trying to build a 32bits version though my SDK > > > is for 64 bits. any idea how to solve that ? > > > > > > Thanks for your attention. > > > Matt > > > ___________________________________________________________________________ > > > Sent via: Wireshark-dev mailing list <[email protected]> > > > Archives: http://www.wireshark.org/lists/wireshark-dev > > > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > > > mailto:[email protected]?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
