On Wednesday 16 November 2011, Dan Kegel wrote: > On Wed, Nov 16, 2011 at 9:43 AM, Alexander Neundorf > > <a.neundorf-w...@gmx.net> wrote: > >> I suspect that the only way to make source code control > >> plugins happy is to link to dummy projects like you > >> do for the main source directory. > >> And then there's no need for those individual source file links. > > > > AFAIK svn etc. work only if you either build in-source, or in the > > additional in-source project. > > I.e. AFAIK it doesn't work in the build tree project. > > Then don't.
Don't what ? > My users expect each top level source directory to What is a top level source directory ? > have a top level eclipse project connected to svn. They will > do all their svn and editing via those top-level source projects. > They expect Eclipse to rebuild when they click "Build Project" > in the build tree project, so the build tree project has to link > to the source projects. It does that, right ? Or would you expect it do it in a different way ? > I already posted a shell script that does this for my special case. > I'm not quite sure how the cdt generator would figure out how > what directories to create phony source projects for, but maybe > it's something like I'd go with the one link to each subproject. So if you want a link, add a project() call to the respective CMakeLists.txt. Alex -- 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