Is it just me, or is CMake's "option" command of limited use?
For one thing, there appears to be no way to specify an option on the command
line, unlike with autoconf, where you can specify --enable-XXX or
--disable-XXX, or specify --withXXX with or without a value or specify
--without=XXX?
Fo
On Fri, Sep 24, 2010 at 05:33:25PM -0700, Scott Mueller wrote:
> Thank you for your response. I'm working with a multi-layered protocol
> that relies on TCP/IP, and in some cases the contiguous payload that I
> need to work with is spread out across several well-formed messages.
Have you looked
Hello Stephen,
Thank you for your response. I'm working with a multi-layered protocol
that relies on TCP/IP, and in some cases the contiguous payload that I
need to work with is spread out across several well-formed messages. In
each of these messages, I parse out the headers in order to determine
On Fri, Sep 24, 2010 at 01:12:17PM -0700, Scott Mueller wrote:
> I have messages that are split up on a size boundary
What exactly do you mean? That within a captured packet in Wireshark,
each message you need to dissect starts a certain byte positions or...?
> This is great, because I then pa
On Sep 24, 2010, at 3:38 PM, Alex Lindberg wrote:
> My intent is to import some detailed logging data into a libpcap file then
> create wireshark dissectors to evaluate the log data.
>
> The log data is composed of ASCII hex values that represent various types of
> messages. These messages are
My intent is to import some detailed logging data into a libpcap file then
create wireshark dissectors to evaluate the log data.
The log data is composed of ASCII hex values that represent various types of
messages. These messages are taken from the data, control and packet buss of
our equipment
On Sep 24, 2010, at 2:43 PM, Alex Lindberg wrote:
> I would like to create a libpcap formated file based on custom data formats,
> NOT from a live capture stream. I will also build custom dissectors for this
> data and use a user defined packet type.
>
> Any suggestions?
My first suggestion
I would like to create a libpcap formated file based on custom data formats,
NOT from a live capture stream. I will also build custom dissectors for this
data and use a user defined packet type.
Any suggestions?
Thanks.Alex Lindberg
___
On Sep 24, 2010, at 2:12 PM, Joerg Mayer wrote:
> On Fri, Sep 24, 2010 at 08:41:37PM +, g...@wireshark.org wrote:
>
>> 2) build them with link mode MODULE, not SHARED, on all
>> platforms.
>
> Hmm, the remaining line now reads "set(LINK_MODE_MODULE SHARED)",
> that's not what y
On Fri, Sep 24, 2010 at 08:41:37PM +, g...@wireshark.org wrote:
> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=34243
>
> User: guy
> Date: 2010/09/24 01:41 PM
>
> Log:
> Plugins are not shared libraries, so:
>
> 1) don't set thei SOVERSION - run-time-loaded module
On Fri, Sep 24, 2010 at 3:55 PM, Joerg Mayer wrote:
> Stig: you mentioned problems with XCODE?
Yes. CMake determines to use "-Wl,--as-needed", but the linker does
not like this option.
Any idea what to look for?
--
Stig Bjørlykke
On Sep 24, 2010, at 1:55 PM, john s wolter wrote:
> Gentlemen, is this discussion related to "Virtual WireShark Appliance". If
> not please move it to a new thread.
At minimum, if you're responding to one of the problems-with-CMake messages:
1) don't send them on to John Wolter
and
Gentlemen, is this discussion related to "Virtual WireShark Appliance". If
not please move it to a new thread.
2010/9/24 Stig Bjørlykke
> On Fri, Sep 24, 2010 at 3:55 PM, Joerg Mayer wrote:
> >Stig: you mentioned problems with XCODE?
>
> Yes. CMake determines to use "-Wl,--as-needed", bu
On Sep 24, 2010, at 1:19 PM, H.sivank wrote:
>
>> What happens if we remove all the set_target_properties calls in the
>> CMakeLists.txt files for the plugins - but revert to using MODULE as the
>> link mode for the plugins?
>
> It builds fine !
OK, so I've backed out the change to the top-l
> What happens if we remove all the set_target_properties calls in the
> CMakeLists.txt files for the plugins - but revert to using MODULE as the link
> mode for the plugins?
It builds fine !
H.sivank
___
Sent via:Wi
Hello Wireshark Dev List,
I've been working with my own dissector for some time now and have run
into a bit of a snag involving memory usage. I have messages that are
split up on a size boundary, so I allocate enough space for the overall
message (yes, I know this is a bit of a red flag) with s
(Again, changing title, but not message ID references.)
On Sep 24, 2010, at 12:12 PM, H.sivank wrote:
> Le 24 sept. 2010 à 15:55, Joerg Mayer a écrit :
>> Btw, can you please provide me with a log what and how things fail when
>> you build with "set(LINK_MODE_MODULE MODULE)" instead of SHARED?
>
Hello All,
I have a working (if basic) dissector plugin running. Is there a way to add
a tap as a part of the plugin, or does it have to be placed in the gtk
directory and compiled with the other taps? Thanks
Hassan
___
Sen
Le 24 sept. 2010 à 15:55, Joerg Mayer a écrit :
> Btw, can you please provide me with a log what and how things fail when
> you build with "set(LINK_MODE_MODULE MODULE)" instead of SHARED?
This is the log with LINK_MODE_MODULE set to MODULE :
Linking C shared module ../../lib/asn1.so
cd /Users/l
(Fixing title, although not fixing References: or In-Reply-To:.)
On Sep 24, 2010, at 6:55 AM, Joerg Mayer wrote:
> H.Sivank:
>What is the exact build environment you are using: gcc + make? If so:
>Gnu make or some Apple provided make?
The Apple-provided make *is* GNU Make (unlike other B
On Fri, Sep 24, 2010 at 12:23:57AM -0400, Joseph Johnson wrote:
> i have see all plugin and pcap file and filter they have i will like
> too see where can i find a plugins or pcap file for camfrog videochat
> system i know that is not soo easy to make bull is it posssible to
> analyze or monito
On Fri, Sep 24, 2010 at 12:47:27PM +0200, H Sivank wrote:
> > I have added a fix in revision 34233, does this work for you?
> >
>
> Work for me :) Thanks for the fix.
Btw, can you please provide me with a log what and how things fail when
you build with "set(LINK_MODE_MODULE MODULE)" instead of
2010/9/24 Stig Bjørlykke
> On Fri, Sep 24, 2010 at 11:28 AM, H Sivank wrote:
> > Hello,
> > My previous post was not clear.
> > It was a *standard* configure log, just to point that the linker does not
> > support "--as-needed".
> > if i do a cmake configure it will fail on big endian test :
>
>
On Fri, Sep 24, 2010 at 12:33 PM, Joerg Mayer wrote:
> That's the type of fix I was hoping for when I rejected the previous one!
> Nicely spotted.
I'm still having problems with --as-needed when building with Xcode,
but not when building with Makefiles.
CMake reports --as-needed is OK when buildi
On Fri, Sep 24, 2010 at 12:25:07PM +0200, Stig Bj?rlykke wrote:
> On Fri, Sep 24, 2010 at 11:28 AM, H Sivank wrote:
> > My previous post was not clear.
> > It was a *standard* configure log, just to point that the linker does not
> > support "--as-needed".
> > if i do a cmake configure it will fai
On Fri, Sep 24, 2010 at 11:28 AM, H Sivank wrote:
> Hello,
> My previous post was not clear.
> It was a *standard* configure log, just to point that the linker does not
> support "--as-needed".
> if i do a cmake configure it will fail on big endian test :
I have added a fix in revision 34233, doe
Hello,
My previous post was not clear.
It was a *standard* configure log, just to point that the linker does not
support "--as-needed".
if i do a cmake configure it will fail on big endian test :
"
CMake Error at /opt/local/share/cmake-2.8/Modules/TestBigEndian.cmake:44
(MESSAGE):
no suitable
On Thu, Sep 23, 2010 at 11:19 PM, Joerg Mayer wrote:
>> -apple_gcc.diff : fix for apple gcc
> This fix is not correct in style. Can you please explain what is going wrong
> here, maybe provide a log? If there is a problem, we need to fix the check in
> cmake/modules/CheckCLinkerFlag.cmake.
When r
28 matches
Mail list logo
