On Friday 05 September 2008, Andreas Pakulat wrote: > On 04.09.08 21:50:03, Alexander Neundorf wrote: ... > > This pops up a dialog in kdevelop saying "This project doesn't contain > > any files yet. Populate it ?" > > > > Why ? The filelist file is not empty. > > For some reason kdevelop thinks it is empty. Looking through the source > all it does is reading the entry from the dom, adding > projectname.kdevelop.filelist and checking wether that file exists. It > will also discover an all-lower-case name and rename that to mixed-case.
I will have a closer look. Beside that, the algorithm looks ok or is there a better way ? ... > > It's not a bug, it's a feature. > > (seriuosly) > > "No files must ever be created in the source dir" (could be read-only, or > > intended to be packaged as a source package, without any additional > > files, or different build dirs could use different IDE settings, etc.) > > I agree - in the general case. But I hope you can agree that its not > quite good to loose all those customizations one does to the project. > And some of them are completely unrelated to the building process - like > environment variables for execution. Well, yes, but the cmake devs are very strict with that requirement that no file must ever be written into the source directory, and I understand and in the meantime also agree with the reasoning. So, yes, this is somewhat inconvenient but I think it's correct. Alex _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake