Elminate the circularity. You'll drive yourself mad. :-)
On Tue, Nov 2, 2010 at 2:38 PM, tmp <[email protected]> wrote: > Hi all, > > I have got some circular dependencies in my source that origin from > internal cache variables managed in different parts of my project. > Unfortunately there is no correct order to include the subprojects: > Sometimes A B C would be correct, sometimes B C A, sometimes C A B. > > At the moment I check, if the affected variables have changed during the > inclusion of the subprojects. > If there has been a change I issue an error message telling the user to > re-run configure. > If the variables have not changed, I can be sure, that all subprojects act > on the same > settings and no error is issued. > > I'm looking for a neater solution. Ideally I would want to start over the > configure step, so that > everything works out fine and no direct action from the user is required. > > Regards > > tmp > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake > _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
