Re: [Wireshark-dev] RPM build - configure parameters
Hi Tomas, On Fri, Sep 12, 2008 at 4:11 AM, Kukosa, Tomas [EMAIL PROTECTED]wrote: Hi, when I build RPM with following sequence ./autogen.sh ./configure parameters make rpm-package it allways calls ./configure script inside rpm packaging with fiexed parameters --with-ssl=/usr --with-krb5 (see packaging/rpm/SPECS/ wireshark.spec.in) Yeah, with rpm packaging and autotools, we're loosing a little bit of our time as the rpm package build has to do the configure - since it is compiling the sources from scratch - but before being able to do so, we - as developers - have to create the specfile which is done by the configure process as well. ;) The egg and the chicken ... you know :) would it be somehow possible to pass parameters from ./configure parameters called before make rpm-package to ./configure called inside rpm packaging? Yes, of course! As ./configure parameters is building the specfile, you can modify in such a way, it includes your options. It works the same way as for Makefile.in. Therefore you would have to modify the configure script in order to use AC_SUBST(CONFIG_PARAM) which will be used to substitute @CONFIG_PARAM@ you would put in the wireshark.spec.in. If my exaplanation hasn't been so clear, I guess it will become obvious when taking a look at for example CC_FOR_BUILD in configure.in, Makefile.in and Makefile. Regards, Sebastien Tandel Regards, Tomas ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
[Wireshark-dev] XML Parser
I'm looking to add support for loading vendor extension information into the LLRP protocol dissector (submitted, but not yet accepted). The vendor extension files are XML formatted, and define the structure and content of extensions to the LLRP protocol. The vendor extension XML files would be read when the dissector is initialized, and would produce structures (in memory) that would be used to dissect the protocol extensions. Is there an XML parsing library available to my dissector? Thanks, Matt Poduska Software Engineer, RFID Systems Intermec 550 Second Street SE Cedar Rapids, IA 52401 voice: 319.369.3331 fax: 319.369.3577 ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] RPM build - configure parameters
Hi Tomas, if config.status is yet present in the dist package, another way, less generic but a far lot quicker, would be to use ./config.status in the wireshark.spec.in i.s.o ./configure params Regards, Sebastien Tandel On Fri, Sep 12, 2008 at 4:11 AM, Kukosa, Tomas [EMAIL PROTECTED]wrote: Hi, when I build RPM with following sequence ./autogen.sh ./configure parameters make rpm-package it allways calls ./configure script inside rpm packaging with fiexed parameters --with-ssl=/usr --with-krb5 (see packaging/rpm/SPECS/ wireshark.spec.in) would it be somehow possible to pass parameters from ./configure parameters called before make rpm-package to ./configure called inside rpm packaging? Regards, Tomas ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
Re: [Wireshark-dev] XML Parser
I needed something similar for feature I have been working on for the SMPP dissector. I could not (when I started working on this) find any ready-made XML parser library in the WS tool chain. So, I have shamelessly copied LEGO's good work on the Diamater Diameter dictionary support (which us also based on XML files). It was a bit tough for me (because I have never worked with Lex before), but it was a good learning experience. There is also the XML dissector which (if I remember correctly) uses the lemon parser generator. HTH Abhik. On Fri, Sep 19, 2008 at 6:41 PM, Matt Poduska [EMAIL PROTECTED] wrote: I'm looking to add support for loading vendor extension information into the LLRP protocol dissector (submitted, but not yet accepted). The vendor extension files are XML formatted, and define the structure and content of extensions to the LLRP protocol. The vendor extension XML files would be read when the dissector is initialized, and would produce structures (in memory) that would be used to dissect the protocol extensions. Is there an XML parsing library available to my dissector? Thanks, Matt Poduska Software Engineer, RFID Systems Intermec 550 Second Street SE Cedar Rapids, IA 52401 voice: 319.369.3331 fax: 319.369.3577 ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev ___ Wireshark-dev mailing list Wireshark-dev@wireshark.org https://wireshark.org/mailman/listinfo/wireshark-dev
