[CMake] Issues with CMake + TAU
sindimo
sindimo at gmail.com
Sun Apr 6 07:23:19 EDT 2014
Thanks Eike for the input.
I went with your suggestion and I am using the environment variables now CC
and FC to point to the TAU wrappers.
Just for the record this specific app isn't cross platform, just on Linux.
It's still identifying the TAU wrappers as GNU and not Intel. For now we
can live with forcing the compiler ID to be Intel.
The second issue explained previously is the one more concerning, any hints
on how to get CMake to dump the TAU temporary files (e.g. *.pp.f, *.pp.pdb,
*.pp.inst.f) in the correct output folder instead of the current directory?
None of these variables seem to be honored when dumping the TAU temporary
files (LIBRARY_OUTPUT_PATH, CMAKE_LIBRARY_OUTPUT_DIRECTORY,
CMAKE_Fortran_MODULE_DIRECTORY)
Thanks again for your help.
On Sunday, April 6, 2014, Rolf Eike Beer <eike at sf-mail.de> wrote:
> Am Sonntag, 6. April 2014, 10:31:57 schrieb sindimo:
> > Dear CMake Support,
> >
> > We've been using your wonderful tool for quite some time to do our cross
> > platform builds.
> >
> > We recently started using the TAU profiler and are having some issues
> when
> > integrating it with CMake and would appreciate your help with it please.
> >
> > We set our compilers in CMake to the TAU wrappers:
> >
> > set (CMAKE_Fortran_COMPILER
> > /red/cmt3/vol5/tau/tau_installation/x86_64/bin/tau_f90.sh)
>
> I don't read on ;) Are you doing this in a toolchain file? Otherwise do it
> either there or using the environment variables (CC, CXX, and so on). If
> you
> start fiddling with the compiler inside a project environment that usually
> means trouble.
>
> Eike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20140406/84663b19/attachment.html>
More information about the CMake
mailing list