Re: [Wireshark-commits] rev 52194: / /trunk/cmake/modules/: FindCARES.cmake FindGCRYPT.cmake FindGEOIP.cmake FindGLIB2.cmake FindGMODULE2.cmake FindGNUTLS.cmake FindGTHREAD2.cmake FindGTK2.cmake FindKERBEROS.cmake ...

[Graham Bloice <graham.bloice () trihedral com>]

On 24 September 2013 10:17, Joerg Mayer <jmayer () loplof de> wrote:

> On Mon, Sep 23, 2013 at 05:32:38PM -0700, Gerald Combs wrote:
> > Would it make things easier for either of you if you could get useful
> > answers from pkg-config on Windows?
>
> Sure! The problem to solve here is how to handle the different install
> places (not everyone will find c:\wireshark\ a convenient place where to
> put the Wireshark-winXX-libs directory). In my current cmake install I've
> created an (environment) variable to specify that base path.
> Apart from that: it would be helping because pkgconfig will allow us to
> get additional information like other required libs, compile flags etc.
As Jorg says, the main issue right at the start is the location of stuff,
does pkg-config give you that, or is it more oriented around how the
package was built and configured?  I'm not at all familiar with pkg-config.

My proto-plan at the moment is that the env installer\updater
(chocolatey??) will grab all the required bits and store them somewhere
(possibly configurable by the user) and then provide that location(s) as a
hint(s) to CMake (env var is too ephemeral for me, probably a file) which
can then go and do its thing.

Graham

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe