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
I was able to compile VVenC with VTune as follows.
//Flags used by the CXX compiler during all build types.
CMAKE_CXX_FLAGS:STRING=-I/opt/intel/oneapi/vtune/2023.0.0/include
//Flags used by the linker during all build types.
CMAKE_EXE_LINKER_FLAGS:STRING=-L/opt/intel/oneapi/vtune/2023.0.0/lib64 -Wl,-Bstatic -littnotify -Wl,-Bdynamic
//Path to the installation directory of Intel VTunes
ITT_PATH:STRING=/opt/intel/oneapi/vtune/2023.0.0
It just works!™
The only constant is change.
The text was updated successfully, but these errors were encountered:
adamjw24
changed the title
Intel® VTune™ Profiler
Intel® VTune™ Profiler 2023
Jan 24, 2023
Hm... We're still on the old version, sth. around 2020, so cannot really either test or change (since this feature is actually mostly catered for the current developers).
Is there any way to detect which version you have? If so, maybe another if could be added.
It would be great if you could have a look and do a merge request.
Worst case, just add comments in CMakeLists on how to make it work with the new VTunes. If someone is looking for that feature, I'd assume the know how to edit it.
Recently, the VTune installation location has been changed. Please check:
https://www.intel.com/content/www/us/en/developer/tools/oneapi/vtune-profiler.html
I was able to compile VVenC with VTune as follows.
//Flags used by the CXX compiler during all build types.
CMAKE_CXX_FLAGS:STRING=-I/opt/intel/oneapi/vtune/2023.0.0/include
//Flags used by the linker during all build types.
CMAKE_EXE_LINKER_FLAGS:STRING=-L/opt/intel/oneapi/vtune/2023.0.0/lib64 -Wl,-Bstatic -littnotify -Wl,-Bdynamic
//Path to the installation directory of Intel VTunes
ITT_PATH:STRING=/opt/intel/oneapi/vtune/2023.0.0
It just works!™
The only constant is change.
The text was updated successfully, but these errors were encountered: