d/install in there, then go back to your containing project, and it's
> already up to date.
>
> To each his own... Good luck.
>
>
> HTH,
> David C.
>
>
>
> -----Original Message-
> From: NoRulez
> To: David Cole
> Cc: cmake
> Sent: Wed, Mar 19, 2
Make mods in there, and build/install in
there, then go back to your containing project, and it's already up to
date.
To each his own... Good luck.
HTH,
David C.
-Original Message-
From: NoRulez
To: David Cole
Cc: cmake
Sent: Wed, Mar 19, 2014 9:48 am
Subject: Re: [CMake]
Ok, so the only "workaround" to archive this is to use "file(GLOB_RECURS...)"
and rebuild the changed external project. Right?
Best Regards
> Am 19.03.2014 um 12:44 schrieb David Cole :
>
> Well, that sounds like the perfect way to use ExternalProject.
>
> But why do you want to show the sourc
Well, that sounds like the perfect way to use ExternalProject.
But why do you want to show the sources in Visual Studio? Just for ease
of looking at them?
As I said in my earlier reply... even if we showed the sources, editing
them would not trigger a rebuild of the external project. The
dep
Because the external projects depends on different library versions than the
"SuperProject". Maybe I misconfigured something, but i don't know an
alternative.
E.g.: super project (AA) builds with version 9 of library X.
The external project B requires version 5 of library X and had some source
Why do you want to do that?
The ExternalProject will not rebuild correctly when you modify these
source files... Unless you are forcing the build step to run every
single time.
You are using ExternalProject as if it were NOT external. Why not just
use add_subdirectory instead and have an "in
I've added the source files with "file(GLOB_RECURSE..." and set source file
property for each of these files with HEADER_FILE_OLY to TRUE.
It seems to work, but I'm not sure if this is the right way.
> Am 17.03.2014 um 08:49 schrieb NoRulez :
>
> Hello,
>
> if I add an external project with E
