mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 18:13:01 +00:00
ed322feb84
clearer what they mean: - They all have VGCONF_ prefixes now, to indicate they come out of configure.in (and are clearly distinguished from the VGA_/VGO_/VGP_ #defines passed in to C files). - The ones that refer to the primary *or* secondary platform have _INCLUDES_ in them. - The ones that are in all-caps have a _CAPS suffix. So, for example, what was VGP_X86_LINUX is now VGCONF_PLATFORMS_INCLUDE_X86_LINUX, which is more verbose but also a lot clearer. The names of the #defines used in the C files (VGA_x86, VGO_linux, etc) are unchanged. cputest.c: changed to reflect the Valgrind installation's capabilities, rather than the machine's capabilities. In particular, if --enable-only32bit is used on a 64-bit machine, then this program will claim to only support 32-bits. Also use the VGA/VGO/VGP macros which are clearer than the __i386__ ones. (This is partially merged from the DARWIN branch.) configure.in: clean up the comments, distinguish different sections more clearly, and generally make it more readable. valgrind.pc.in: try to make this more accurate. I doubt anyone's using it. It doesn't appear to be set up to handle dual-architecture builds. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@9031
17 lines
413 B
PkgConfig
17 lines
413 B
PkgConfig
prefix=@prefix@
|
|
exec_prefix=@exec_prefix@
|
|
libdir=@libdir@
|
|
includedir=@includedir@/valgrind
|
|
arch=@VGCONF_ARCH_PRI@
|
|
os=@VGCONF_OS@
|
|
platform=@VGCONF_ARCH_PRI@-@VGCONF_OS@
|
|
valt_load_address=@VALT_LOAD_ADDRESS@
|
|
|
|
Name: Valgrind
|
|
Description: A dynamic binary instrumentation framework
|
|
Version: @VERSION@
|
|
Requires:
|
|
Libs: -L${libdir}/valgrind/@VGCONF_ARCH_PRI@-@VGCONF_OS@ -lcoregrind -lvex -lgcc
|
|
Cflags: -I${includedir}
|
|
|