You can avoid the work by adding a GLOB * wildcard for header files, but explicitly specifying every individual file seems recommended indeed.
Once you have the cmake project up and running, you usually only add a few .cpp or .h files at a time, so the incremental effort usually isn't much. This doesn't seem to be a good reason to favor scons over cmake. Thanks, Erwin 2010/1/10 joe <joe...@gmail.com> > Yeek. That's horrible. I wonder how hard would it be to write some > utility code for the cmakefiles that scans for #include statements. > This sort of thing is exactly why I stick with scons, despite it's > horrific speed problems. :-/ I'm even tempted to rewrite our scons > files to use waf instead sometimes. > > Joe > > > On Sat, Jan 9, 2010 at 4:50 PM, Erwin Coumans <erwin.coum...@gmail.com> > wrote: > >> INC is to tell the compile what include directories to use. Without it > the > >> source won't compile. > >> > >> If you don't specify the headerfiles, the source compiles, links and > runs, > >> but > >> dependencies and program database (MSVC) won't work properly. > >> > >> > >> 2010/1/9 Erwin Coumans <erwin.coum...@gmail.com> > >> > >>> > >>> No, you need to specify the headerfiles (either by individual name or > GLOB > >>> * wildcard) > >>> for dependencies and certain features to work properly > >>> (for example MSVC won't find definitions properly (right-click 'goto > >>> definition'), > >>> if headerfiles are missing from the cmake generated projectfiles. > >>> > >>> Thanks, > >>> Erwin > >>> > >>> > >>> 2010/1/9 Nicholas Bishop <nicholasbis...@gmail.com> > >>> > >>> Really? I was pretty sure you just have to make sure the header paths > >>>> are set using SET(INC path1 path2 ...)), and it's only source files > >>>> that have to be explicitly named or wildcarded. > >>>> > >>>> -Nicholas > >>>> > >>>> On Sat, Jan 9, 2010 at 2:18 PM, Erwin Coumans < > erwin.coum...@gmail.com> > >>>> wrote: > >>>> > All headerfiles have to be included, either manually (each by name) > or > >>>> using > >>>> > a wildstar (using GLOB). I suppose GLOB with a wildcard is what you > >>>> refer to > >>>> > as 'header paths'? > >>>> > > >>>> > Thanks, > >>>> > Erwin > >>>> > > >>>> > > >>>> > 2010/1/9 joe <joe...@gmail.com> > >>>> > > >>>> >> So in cmake, do you have to include the header paths or actually > list > >>>> >> the header files themselves? > >>>> >> > >>>> >> Joe > >>>> >> > >>>> >> On Thu, Jan 7, 2010 at 3:37 PM, Erwin Coumans < > erwin.coum...@gmail.com > >>>> > > >>>> >> wrote: > >>>> >> > By the way, if OpenCollada breaks the cmake build system, it > should > >>>> be > >>>> >> > disabled I think. > >>>> >> > Hopefully that motivates someone who needs OpenCollada to fix it. > >>>> >> > > >>>> >> > Can someone disable OpenCollada by default it in cmake? > >>>> >> > Thanks, > >>>> >> > Erwin > >>>> >> > > >>>> >> > > >>>> >> > > >>>> >> > 2010/1/7 Ken Hughes <khug...@pacific.edu> > >>>> >> > > >>>> >> >> Since this thread is now about build systems, can we please > change > >>>> the > >>>> >> >> subject line? > >>>> >> >> > >>>> >> >> Ken > >>>> >> >> > >>>> >> >> Campbell Barton wrote: > >>>> >> >> > Not sure what dependency updates are exactly - if files are > added > >>>> you > >>>> >> >> > need to run "cmake ." in the build dir but aside from that I > never > >>>> had > >>>> >> >> > any dep propblems. > >>>> >> >> > > >>>> >> >> > I'm tempted to install Windows just to get rid of the MSVC > Project > >>>> >> >> > files and have CMake create propper debug builds... it cant be > >>>> that > >>>> >> >> > hard can it? > >>>> >> >> > > >>>> >> >> > @Martin, my experience with using scons and eclipse isnt so > good, > >>>> it > >>>> >> >> > works OK but a bit annoying to setup, I recall I needed to > have > >>>> >> >> > eclipse call a shell script that called scons. > >>>> >> >> > > >>>> >> >> > Eclipse + Cmake is nicer, and takes the work out of setting up > the > >>>> >> >> > project each time. especially if you want to switch to > developing > >>>> in > >>>> >> >> > branches for a bit. > >>>> >> >> > > >>>> >> >> > On Thu, Jan 7, 2010 at 3:52 PM, Martin Poirier < > the...@yahoo.com> > >>>> >> wrote: > >>>> >> >> > > >>>> >> >> >> --- On Thu, 1/7/10, Erwin Coumans <erwin.coum...@gmail.com> > >>>> wrote: > >>>> >> >> >> > >>>> >> >> >> > >>>> >> >> >>> New developers (and myself) can browse and debug code much > >>>> >> >> >>> easier in > >>>> >> >> >>> an IDE such as msvc, Xcode or K develop, in my opinion. And > >>>> >> >> >>> manual > >>>> >> >> >>> updating projectfiles is a waste of time. > >>>> >> >> >>> > >>>> >> >> >> It's very easy to use Eclipse (with CDT) with scons. K > Develop > >>>> was > >>>> >> >> pretty easy to setup too the last time I tried. There was no > project > >>>> >> files > >>>> >> >> to update or anything. > >>>> >> >> >> > >>>> >> >> >> Martin > >>>> >> >> >> > >>>> >> >> >> > >>>> >> >> >> > >>>> >> __________________________________________________________________ > >>>> >> >> >> Yahoo! Canada Toolbar: Search from anywhere on the web, and > >>>> bookmark > >>>> >> >> your favourite sites. Download it now > >>>> >> >> >> http://ca.toolbar.yahoo.com. > >>>> >> >> >> _______________________________________________ > >>>> >> >> >> Bf-committers mailing list > >>>> >> >> >> Bf-committers@blender.org > >>>> >> >> >> http://lists.blender.org/mailman/listinfo/bf-committers > >>>> >> >> >> > >>>> >> >> >> > >>>> >> >> > > >>>> >> >> > > >>>> >> >> > > >>>> >> >> > > >>>> >> >> > >>>> >> >> _______________________________________________ > >>>> >> >> Bf-committers mailing list > >>>> >> >> Bf-committers@blender.org > >>>> >> >> http://lists.blender.org/mailman/listinfo/bf-committers > >>>> >> >> > >>>> >> > _______________________________________________ > >>>> >> > Bf-committers mailing list > >>>> >> > Bf-committers@blender.org > >>>> >> > http://lists.blender.org/mailman/listinfo/bf-committers > >>>> >> > > >>>> >> _______________________________________________ > >>>> >> Bf-committers mailing list > >>>> >> Bf-committers@blender.org > >>>> >> http://lists.blender.org/mailman/listinfo/bf-committers > >>>> >> > >>>> > _______________________________________________ > >>>> > Bf-committers mailing list > >>>> > Bf-committers@blender.org > >>>> > http://lists.blender.org/mailman/listinfo/bf-committers > >>>> > > >>>> _______________________________________________ > >>>> Bf-committers mailing list > >>>> Bf-committers@blender.org > >>>> http://lists.blender.org/mailman/listinfo/bf-committers > >>>> > >>> > >>> > >> _______________________________________________ > >> Bf-committers mailing list > >> Bf-committers@blender.org > >> http://lists.blender.org/mailman/listinfo/bf-committers > >> > > _______________________________________________ > > Bf-committers mailing list > > Bf-committers@blender.org > > http://lists.blender.org/mailman/listinfo/bf-committers > > > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers