[CMake] Best practices when using CMake 2.6 and Eclipse CDT 6.0

[Romain CHANU]

Yes I agree with you. It would be nice to hide these CMake generated files
(except those that are generated by your CMakeLists.txt and used for
compilation purpose, e.g. files generated by external command like
CodeSynthesis XSD).

One more thing, about the version control integration (SVN) in Eclipse using
an out-of-source build (cf .
http://www.cmake.org/Wiki/Eclipse_CDT4_Generator_Development), do I still
need to create two different projects? One being my source code from my
repository and the other one being my "build" directory?

Is there any fix regarding this issue in the incoming 2.8 version? Or any
existing work-around?

Thank you!

Romain

2009/10/6 Philip Lowman <philip at yhbt.com>

>
>
> On Mon, Oct 5, 2009 at 1:48 AM, Romain CHANU <romainchanu at gmail.com>wrote:
>
>> Hi,
>>
>> Thank you for your replies. There is still something unclear for me.
>>
>> Let me describe the structure of my project (SVN project):
>>
>> branches/
>> build/
>> tags/
>> trunk/
>>
>> I run the cmake command in the build directory (i.e "cmake ../trunk")
>> which generates the .project and .cproject, as well as all the CMake files
>> generated by the cmake command.
>>
>> When I import the project in Eclipse (I import the build directory which
>> contains the Eclipse files), here is the structure within Eclipse:
>>
>> Binaries/
>> Includes/
>>  myProject/files_in_trunk
>> generated_cmake_file_1
>> generated_cmake_file_2
>> ...
>> ...
>> generated_cmake_file_N
>>
>> As I said in my first post, the import is dirty as I have all the
>> generated files in the "main" directory. What I would like to have is the
>> following structure:
>>
>> Binaries/
>> Includes/
>> build/ (and the generated cmake files...)
>> myProject/files_in_trunk
>>
>> I may miss something or misunderstand the process. Could anyone tell me
>> what's the best way to operate?
>>
>
> I have the same thing here.  I usually just expand myProject (source tree)
> and forget about what's below.  It would be nice if there was a way to hide
> CMake generated cruft from the Eclipse project.
>
> --
> Philip Lowman
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20091007/4a92a84d/attachment.htm>