[netsa-tools-discuss] silk_config
Mark Thomas
mthomas at cert.org
Tue May 24 16:45:09 EDT 2016
John-
silk_config does include a lot of extra junk in the output for the
compiler/include-flags switches.
I think
silk_config --include | awk '{print $1}'
is probably sufficient.
The library switches seem clean.
-Mark
-----Original Message-----
From: John Green <johng at csirt.ja.net>
Date: Tue, 24 May 2016 16:08:07 +0100
To: "netsa-tools-discuss at cert.org" <netsa-tools-discuss at cert.org>
Subject: [netsa-tools-discuss] silk_config
Hi,
What is the correct way of determining the silk library configuration
when building third party executables? Silk doesn't appear to ship
with a pkg-config file, unlike some other netsa libraries like
libfixbuf.
I've been trying to use silk_config, reusing the m4 macro from
pipeline, but this seems to return far more information than is
necessary and pollutes my own Makefile with lots of unwanted/duplicate
flags.
Thanks in advance,
John
More information about the netsa-tools-discuss
mailing list