<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 18, 2011, at 11:23 AM, David Cole wrote:</div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div class="gmail_quote"><blockquote class="gmail_quote" style="margin-top: 0pt; margin-right: 0pt; margin-bottom: 0pt; margin-left: 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex; "><div><div class="h5">><br>> That is not entirely true....<br>><br>> Things like EXECUTABLE_OUTPUT_PATH and target location properties have<br>> to work without an extra install step. What do you mean CMake expects<br>> to find things in install locations? CMake does need to be able to<br>> find executables after the build is run. It also needs to be able to<br>> place them via location properties.<br><br><br></div></div>Take for example a simple test case that just builds one source file into an executable via"<br> ADD_EXECUTABLE(main main.c)<br>When I use cmake to create a Makefile, the resulting main executable is placed in the build directory tree next to the Makefile.<br>When I use cmake to create a xcode project, the resulting main executable is placed in a subdirectory named Debug of the build directory tree.<br><br>The method cmCoreTryCompile::FindOutputFile() seems to know about this because it looks for executables in the build directory then in <build directory>/Debug and <build directory>/Release.<br><br>None of these locations are the "native" location where Xcode would put a build result. So, I need to create xcode projects that place/copy the resulting executables somewhere that cmake universe expects.<br><br>Now I am wondering if I should add a copy-files-phase in the executable target to copy the resulting binary to the build directory. That would make xcode output be like Makefile output.<br><font color="#888888"><br>-Nick<br><br><br></font></blockquote></div><br>Where does the Xcode equivalent of "add_executable(main main.c)" naturally go?<br></span></blockquote></div><div><br></div>It depends on some global xcode settings. Some users have a one location in which all projects put their final projects. Some users have a build/Debug and build/Release directory next to the xcode project file. <div><br></div><div>That is why I'm thinking that if cmake's model is to have the final executable put into cmakes build directory, that I should just let xcode build it where the user wants, then copy it to where cmake wants. That way both models are happy.</div><div><br></div><div>-Nick</div><div><br><div><br></div><div><br></div><div><br></div></div></body></html>