<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>Essentially, I'd like to hear your views on handling resource copying. Is<br>there an obvious method I've overlooked? What are other projects doing to<br>handle resources? Any ideas with respect to other methods of handling resources?<br></div></blockquote><div><div><br></div><div><br></div><div>You could do your resources like this:</div><div><br></div><div>set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)</div><div><br></div><div>set(inres ${CMAKE_CURRENT_SOURCE_DIR}/myres.txt)</div><div>set(outres ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${CMAKE_CFG_INTDIR}/myres.txt)</div><div>add_custom_command(OUTPUT "${outres}"</div><div> COMMAND "${CMAKE_COMMAND}" -E copy "${inres}" "${outres}")</div><div><br></div><div>add_library(foo foo.cpp ${outres})</div><div><br></div><div>The custom command will be part of building the library, and will run anytime myres.txt is out-of-date.</div><div>You could make a macro or function if you need to repeat that code often.</div><div><br></div><div>Also, installers can easily be made with things scattered around a build tree. The cmake install() commands help you put it where you want in the installer. So, I suggest saving your install() commands for making installers, not for handling external libraries.</div><div><br></div><div>Clint</div></div></div></body></html>