Depending on the use I find it easier to just build in the source
directory.. (easier to just type vi filename.c instead of vi
../../../foo/bar/bar/filename.c ).

As for the clang warnings even if I use a dedicated build directory:

[100%] Building C object CMakeFiles/time-test.dir/sample/time-test.c.o
clang: warning: argument unused during compilation: '-I
/Users/trond/compile/couchbase/obj/include'
clang: warning: argument unused during compilation: '-I
/Users/trond/compile/couchbase/libevent/include'
clang: warning: argument unused during compilation: '-I
/Users/trond/compile/couchbase/libevent/compat'
clang: warning: argument unused during compilation: '-I
/Users/trond/compile/couchbase/libevent'

from: trond@ok:1031> cmake ../libevent && gmake

trond@ok:1031> clang --version
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
Target: x86_64-apple-darwin13.0.0
Thread model: posix




On Fri, Feb 14, 2014 at 2:50 PM, JoakimSoderberg
<notifications@github.com>wrote:

> In .gitignore:
>
> > @@ -99,3 +99,18 @@ libevent_openssl.pc
> >  /test/test-changelist
> >  /test/test-fdleak
> >
> > +
>
> Ok, that is definantly not recommended. Maybe it works, but I don't see
> why you would ever want to do that. This addition to the ignore file just
> seems unnecessary.
>
> These warnings you're getting with CLang might be because you're building
> "in source". I haven't seen them on OSX at least.
>
> In short, use "out of source" build instead, much nicer. Thats' what the
> CMake project was written for.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/libevent/libevent/pull/108/files#r9748478>
> .
>



-- 
Trond Norbye