> Thing is: will you never forget? And it prevents stray files from being
> picked up (as you experienced). Also, you get an immediate response if a file
> is missing, and not just when the compiler complains about a missing header
> or you get undefined references during the linking stage.
O
On 1. Jul, 2010, at 10:15 , Diablo 666 wrote:
>
> Hi,
>
> thanks for your reply.
>
>> 1. Never use GLOB_RECURSE. It's evil. E.g. if you add or remove source
>> files, CMake has no way of knowing that it should be re-run.
> I have tested rerunning cmake manually and it worked out well. (Testca
Hi,
thanks for your reply.
> 1. Never use GLOB_RECURSE. It's evil. E.g. if you add or remove source files,
> CMake has no way of knowing that it should be re-run.
I have tested rerunning cmake manually and it worked out well. (Testcase: I
added a new .cpp file to the build) I either have to ch
On 1. Jul, 2010, at 9:45 , Diablo 666 wrote:
>
> Hi,
>
> I'm currently trying to use the following line to include all source files
> into my build:
>
> file (GLOB_RECURSE Files_CPP *.cpp)
> add_executable(test
>${Files_CPP}
> )
>
> Everything runs fine while using an out-of-source build
Hi,
I'm currently trying to use the following line to include all source files into
my build:
file (GLOB_RECURSE Files_CPP *.cpp)
add_executable(test
${Files_CPP}
)
Everything runs fine while using an out-of-source build, but for in-source
builds these lines include .cpp files from the CM
