> No, AFAIK this is fix and you can't change it. > > Why do you want to do that ? > (I recommend you just get used to the location of > the object files).
I want to add the gcc options for gcov in Makefile. The gcc flags dumps the *.gcno files at the location of .o files. So, if you run the gcov on .c files, then these files should be in the current directory where from you are running gcov. With existing CMake Framework for .o files, either one should copy *.gcno files in current directory or should run gcov from .O files directory. If any othjer option is available? Do help me out!! regards Amit --- Alexander Neundorf <[EMAIL PROTECTED]> wrote: > On Monday 12 November 2007, Amit C. Kr. Saluja > wrote: > > Eric, > > Thanks for this info! > > > > > EXECUTABLE_OUTPUT_PATH > > > LIBRARY_OUTPUT_PATH > > > > These are global CMake variables. If we change it > then > > the EXECUTABLE & LIBRARY path of all the exe and > libs > > changes but not for .os The.os are still generated > in > > CMakeFiles/ directory. > > > > Can CMAKE_CURRENT_BINARY_DIR could do something? > > No, AFAIK this is fix and you can't change it. > > Why do you want to do that ? > (I recommend you just get used to the location of > the object files). > > Alex > _______________________________________________ > CMake mailing list > CMake@cmake.org > http://www.cmake.org/mailman/listinfo/cmake > ____________________________________________________________________________________ Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/ _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake