Into config.nmake, there is :
!IF $(MSC_VER_REQUIRED) >= 1400
DLL_LDFLAGS = /MANIFEST:no
!ENDIF
Comment the 2nd line, you will have a manifest.
But the explicit test seems to mean that manifest is no more necessary
for MSVC2008 and MSVC2008EE ?
Olivier
yvanmmailbox-web@xxxxxxxx a �crit :
It is possible, I encountered this problem when I was coding my plugin
for WS 1.0.7.
The problem is I use know 1.2.0 source code, with Mic. VC++2008EE, and
when I compile I don't have any manifest file generated any more.
I tried to attach the old manifest to my new plugin (the only
difference is I compiled in the new source code directory, with my old
files), but it doesn't work.
How can I generate a manifest file in 1.2.0 plugin code?
Thanks
Yvan
------------------------------------------------------------------------
*De :* wsgd <wsgd@xxxxxxx>
*� :* Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
*Envoy� le :* Mardi, 23 Juin 2009, 20h31mn 06s
*Objet :* Re: [Wireshark-dev] Re : Plugin compatibility with Portable
version
This error message could be a manifest problem.
The manifest must be :
- into the dll directory
- directly inside the dll (using mt.exe -manifest
<dll_name>.dll.manifest -outputresource:<dll_name>.dll;2)
Olivier
yvanmmailbox-web@xxxxxxxx <mailto:yvanmmailbox-web@xxxxxxxx> a �crit :
> Sure, I have another one, my main plugin afdx.dll that works. This one
> is necessary for bite.dll working, but I put both in the folder, like
> I do on my installed version, and I have the error message.
>
> That's why I need some ways to search the problem. What are the main
> differences between the portable version and the installed version
> (except the folders) that could have a link with plugins?
> Does my installed version could create problems for the portable
version?
>
> Note: I put the plugins in the "Global plugins" folder and not in the
> "Personal plugins" folder, which does not exist.
>
> Thanks
>
> Yvan
>
> ------------------------------------------------------------------------
> *De :* Graeme Lunt <graeme@xxxxxxxxxxx <mailto:graeme@xxxxxxxxxxx>>
> *� :* Developer support list for Wireshark
<wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>>
> *Envoy� le :* Mardi, 23 Juin 2009, 14h58mn 10s
> *Objet :* Re: [Wireshark-dev] Plugin compatibility with Portable version
>
> Hi,
>
> There should be no particular problem using custom plugins with the
> WiresharkPortable.
>
> As you say "one of them", can I assume that you have got other plugins
> to work?
>
> Is it perhaps that bite.dll requires some other dlls to be present?
>
> Graeme
>
> 2009/6/23 <yvanmmailbox-web@xxxxxxxx
<mailto:yvanmmailbox-web@xxxxxxxx> <mailto:yvanmmailbox-web@xxxxxxxx
<mailto:yvanmmailbox-web@xxxxxxxx>>>
>
> Hi list,
>
> I developed plugins that works well on standard Windows version of
> Wireshark (1.2.0), but one of them can't be loaded on the portable
> version (same version number). I have the following error:
> Couldn't load module
> F:\Softs\WiresharkPortable\App\Wireshark\plugins\1.2.0\bite.dll:
> `F:\Softs\WiresharkPortable\App\Wireshark\plugins\1.2.0\bite.dll':
> Le module sp�cifi� est introuvable. (can't find specified module)
>
> Does anyone have an idea what could be the problem?
>
> thanks a lot
>
> Yvan
>
>
>
___________________________________________________________________________
> Sent via: Wireshark-dev mailing list
> <wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>
<mailto:wireshark-dev@xxxxxxxxxxxxx <mailto:wireshark-dev@xxxxxxxxxxxxx>>>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx
<mailto:wireshark-dev-request@xxxxxxxxxxxxx>
> <mailto:wireshark-dev-request@xxxxxxxxxxxxx
<mailto:wireshark-dev-request@xxxxxxxxxxxxx>>?subject=unsubscribe
>
>
>
> ------------------------------------------------------------------------
>
>
___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx
<mailto:wireshark-dev@xxxxxxxxxxxxx>>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx
<mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx
<mailto:wireshark-dev@xxxxxxxxxxxxx>>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx
<mailto:wireshark-dev-request@xxxxxxxxxxxxx>?subject=unsubscribe
------------------------------------------------------------------------
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe