On 2010/04/20, at 15:08, Jaap Keuter wrote:
Hi,
What's wrong with what is written in README.plugins? See
http://anonsvn.wireshark.org/wireshark/trunk/doc/README.plugins
Maybe adding a quick start section, or would it be too dangerous?
I think that could help something happen in wireshark very fast, that
could attract more plugin developers.
Any viable additions/fixes are welcome as a patch in Bugzilla.
Thanx,
Jaap
On Tue, 20 Apr 2010 10:42:14 +0100, Bruno Matos
<bruno.matos@xxxxxxxxx>
wrote:
Hello,
In first place, I would like to thank you all the effort and work in
wireshark, it is a every day's tool with very high quality wich
proves
that open source works great.
Now about CMake, thank you once again for the effort to migrate to
CMake, it makes things much more easier.
I had a dissector, that I wanted to build as a plugin. I made a svn
checkout from the trunk, added a new subdirectory in plugins
directory, copied the CMakelists.txt from asn1 plugin, made the
necessary modifications to be compatible with my new plugin, added
the
new subdirectory to the root CMakelists.txt file and just build the
new target. The target was build successfully and there it was my new
'plugin'.so (linux) file. Is that simple, or am I missing something?
If it is, do you think that would be nice to put these steps
somewhere?
Thank you.
Regards.
--
Bruno Matos
bruno.matos@xxxxxxxxx
___________________________________________________________________________
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
___________________________________________________________________________
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
Regards.
--
Bruno Matos
bruno.matos@xxxxxxxxx
