Wireshark · Wireshark-dev: Re: [Wireshark-dev] Using the PCRE library for Windows??

[Alex Lindberg <alindber@xxxxxxxxx>]

True, but since pcre is removed from the windows library download site, should the PCRE option still be in the config.nmake file?

In epan/ftypes/*c files, both the pcre lib and Gtkregex are  used causing the developer to take both into account.  IMHO, ugly.

In my case, I use the regcomp set of functions to build a library of regex expressions to parse my data sets.  If the pcre lib is available for Linux, why not for windows. I would request that the pcre libs/bin file be restored to the 1.4 and 1.6 (trunk) resources.

Thanks.
Alex Lindberg

--- On Wed, 6/22/11, Anders Broman <anders.broman@xxxxxxxxxxxx> wrote:

From: Anders Broman <anders.broman@xxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] Using the PCRE library for Windows??
To: "Developer support list for Wireshark" <wireshark-dev@xxxxxxxxxxxxx>
Date: Wednesday, June 22, 2011, 9:28 AM

Hi,

Since we don't need it for Windows as it's available trough glib/GTK, it probably got removed. can't you use the Glib/GTK equivalents?

Regards

Anders

---

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Alex Lindberg
Sent: den 22 juni 2011 16:01
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] Using the PCRE library for Windows??

I use the pcre (Perl Compatible Regular Expressions) library, however while the windows version is referenced in config.nmake, it does not exist in the predefined location for Makefile.nmake to install. 

   http://anonsvn.wireshark.org/wireshark-win32-libs/trunk-1.4/packages//pcre-7.0-bin.zip

Suggestions on working around this?

Thanks as always.

Alex Lindberg

-----Inline Attachment Follows-----

___________________________________________________________________________
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