Structure the code such that a project can be imported from Eclipse (i.e. we need ".project", ".cproject", and "Makefile") so that it can be compiled with minimal changes to the Eclipse project settings.
This will also require each of these files to be platform independent.
Structure the code such that a project can be imported from Eclipse (i.e. we need ".project", ".cproject", and "Makefile") so that it can be compiled with minimal changes to the Eclipse project settings.
This will also require each of these files to be platform independent.
Some sites that discuss this:
http://www.drdobbs.com/cpp/cross-platform-cc-development-with-eclip/232300575
http://stackoverflow.com/questions/3811672/setting-up-a-cross-platform-c-project-in-eclipse-with-cross-platform-libraries
Turns out there is a CDT bug that will make this difficult:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=226457
Other ideas:
Have platform specific files that people rename?
For now maybe we should start with Windows.
Last edit: Neal Kruis 2012-10-04
I think this can be accomplished by using CMake and keeping the CMakeLists.txt, the .project and the .cproject files under version control.
I still need to look into the settings in eclipse that we would want to use for standard EPx development. Some ideas:
Perspectives? (I don't think these are stored at the project level)
assigned_to: Neal Kruis