You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Applications of PerfUtils using CMake need to include headers differently depending on whether the application chooses to compile against the "build" copy of PerfUtils or the "install" copy of PerfUtils. At the moment if an application wants to include Cycles.h using the "build" copy, the application would #include "Cycles.h"; if using the "install" copy, the application would #include "PerfUtils/Cycles.h". This means that applications source code can't be agnostic to how a user might want to make PerfUtils available in their build.
In short, it would be beneficial if the include statements for PerfUtils headers were the same regardless of a users installation preferences.
The text was updated successfully, but these errors were encountered:
Applications of PerfUtils using CMake need to include headers differently depending on whether the application chooses to compile against the "build" copy of PerfUtils or the "install" copy of PerfUtils. At the moment if an application wants to include
Cycles.h
using the "build" copy, the application would#include "Cycles.h"
; if using the "install" copy, the application would#include "PerfUtils/Cycles.h"
. This means that applications source code can't be agnostic to how a user might want to make PerfUtils available in their build.In short, it would be beneficial if the include statements for PerfUtils headers were the same regardless of a users installation preferences.
The text was updated successfully, but these errors were encountered: