To whom it may concern,
I'm really excited to use Papi, and have a somewhat esoteric use-case which I haven't been able to find much guidance on. I'd like to use Papi internally within an Intel Pintool. If you're not familiar with Intel's Pin, it's roughly a tool to JIT instrument executables, allowing one to execute arbitrary code between instructions in a workload program.
Pin is a bit weird, in that they require any external dependencies to be compiled with their own C runtime and headers, and they do not support dynamically linking other libraries. In short, this means I need to recompile/link PAPI using Pin's C runtime, into a static library. Building Papi using the generic recommended method looks fairly complicated, so I'm not sure the easiest way to do this. Suppose I have a bunch of compiler/linker flags that I'd like to be included in order to build with PIN, is there a convenient place I can add these to ensure Papi gets built using the right C runtime implementation from Pin?
Please let me know if my question is underspecified, or if more detail would be helpful.
Best wishes,
Nick