The one complaint I have with building in another directory is when working
with emacs. I like to do my make inside of emacs, that way when there is a
compile error message I can click on it from emacs and it takes me right to the
offending line. The only problem is that if I have to close all files after
editing them as emacs gets confused if a file is open, and assumes the build is
where the source file is, so it fails.
Emacs users hate doing extra steps such as closing files ( I hav eto do a
extra key stroke operation for each file that is open (to close file) before
recompiling from the build directory.
--- On Wed, 7/23/08, Thomas Burdick <[EMAIL PROTECTED]> wrote:
From: Thomas Burdick <[EMAIL PROTECTED]>
Subject: Re: [CMake] CMAKE equivalent of qmake's MOC_DIR
To: cmake@cmake.org
Date: Wednesday, July 23, 2008, 11:31 AM
It'd still be nice to specify where these files go, even if its not necessarily
needed. In source builds tend to get messy otherwise.
-Tom
On Tue, Jul 22, 2008 at 4:57 PM, Andreas Pakulat <[EMAIL PROTECTED]> wrote:
On 22.07.08 14:02:06, David Boosalis wrote:
> Hi
>
> The qmake variable MOC_DIR allows you to define where you want the generated
> moc flies to reside. I like to use it as it keeps my source directory clean.
>
> Is there a similar variable with cmake
Thats not really needed with cmake, because cmake allows to do real
out-of-source builds without having to set tons of output dirs
individually. Just create a build dir somewhere, go into it and run
cmake <sourcedir>
Andreas
--
You will be winged by an anti-aircraft battery.
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
