Recently, my design team bought a C / C ++ codebase from a contractor who does not use Eclipse. Basically a large / src tree organized to be created using Autotools, with several top-level build scripts masking some of the complexity of Autotools.
The developers of our project team managed to create the code in Eclipse (Luna) as an Autotools project ... but what is currently causing sadness is that as we start working with this code, the CM project also moves to Jazz / RTC 5 (formal process, not Agile) from ClearCase / ClearQuest.
None of us knows if the code should go to the RTC repository as a fully configured Eclipse project, ready for use by developers.
My reading as a developer is what it should: if it is not, when I upload the code to the workspace of my repository, I should start by entering new .project, .cproject and .autotools files “behind the scenes” to go to a project that indicates the include paths I need, allows me to analyze C / C ++ code and (hopefully) can be reconfigured to create Autotools from Eclipse. It also means that when I deliver the change sets back, it will probably use a lot of workarounds to avoid providing project-specific settings that are not part of the code base, as was developed by CM. Right now, if you keep it as close as possible to the supplied contractor (non-Eclipse) package.
I hope someone can tell me if it is standard practice to use RTC with Eclipse to install one code in RTC in the form of fully configured, ready-to-use Eclipse projects. The language used in the articles I find suggests, for example, talking about “Find and Download Eclipse Projects,” but nothing I see makes it explicit.
source share