Oh wait, since a is in the interface of b, b will always be accompanied by a, even though it's not a dependency. Is that how it works?
On Wed, Jul 23, 2014 at 2:58 PM, Nick Overdijk <n...@astrant.net> wrote: > Thanks for the quick reply, but what if c needs b and b needs a? Adding > "INTERFACE" will then break the build of course, right, since b isn't > really linked to a... Or am I mistaken? > > > On Wed, Jul 23, 2014 at 2:36 PM, Brad King <brad.k...@kitware.com> wrote: > >> On 07/23/2014 08:00 AM, Nick Overdijk wrote: >> > With this https://github.com/NickNick/cmake-dependency-waiting code >> here, why do b wait for a and c wait for b to be build? The object files >> could all be build in parallel right? Not doing it is making my >> distcc-cluster less and less useful the more nodes I add. Is there a way to >> fix or work around >> > this? >> >> See here: >> >> http://www.cmake.org/Bug/view.php?id=14726#c35021 >> http://www.cmake.org/Bug/view.php?id=14726#c35023 >> >> -Brad >> >> >
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
