I am switching to eclipse from Emacs, and trying to set it up in a reasonable way to manage a Python project where part of the code is implemented in C++. In the project, the Python stuff is in one subdirectory, while C++ source code is spread out among a few subdirectories.
I made two Eclipse projects. A C++ project where the source directory is a link to the root directory of my original project. And a PyDev project, where one source directory is a link to the Python subdirectory of the original project, and another source directory is a link to the directory where the C++ makefile dumps the compiled .so file.
It this a reasonable way to do it, or am I overlooking something obvious?
A second question: The original project is under SVN, and should remain that way. The C++ project discovered this automatically, and I can see that it marks modified files as such. But the PyDev project does not appear to have noticed the .svn directories. Can I somehow fix this?
Best regards
Jakob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Seems like a way that works, but why don't you just create a single project for both? (probably create it as a c++ project and later just set it as a python project too: right click project > set as pydev project) and configure the preferences for the source folder from the configuration page.
Usually the organization I use for a project is:
/project
/project/build <- stuff to build the project
/project/docs <- docs for the project
/project/sources
/project/sources/c++ <- c++ source files
/project/sources/bindings <- the bindings that'll wrap c++ for python using something as boost:python
/project/sources/python <- this is the source folder to be specified in pydev
If you do decide to go with eclipse links, just make sure you only use links before the source folder level (pydev won't recognize eclipse links inside a source folder).
As for .svn, you should be able to right click the project > team > share project (but that has nothing to do with pydev).
Cheers,
Fabio
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am switching to eclipse from Emacs, and trying to set it up in a reasonable way to manage a Python project where part of the code is implemented in C++. In the project, the Python stuff is in one subdirectory, while C++ source code is spread out among a few subdirectories.
I made two Eclipse projects. A C++ project where the source directory is a link to the root directory of my original project. And a PyDev project, where one source directory is a link to the Python subdirectory of the original project, and another source directory is a link to the directory where the C++ makefile dumps the compiled .so file.
It this a reasonable way to do it, or am I overlooking something obvious?
A second question: The original project is under SVN, and should remain that way. The C++ project discovered this automatically, and I can see that it marks modified files as such. But the PyDev project does not appear to have noticed the .svn directories. Can I somehow fix this?
Best regards
Jakob
Seems like a way that works, but why don't you just create a single project for both? (probably create it as a c++ project and later just set it as a python project too: right click project > set as pydev project) and configure the preferences for the source folder from the configuration page.
Usually the organization I use for a project is:
/project
/project/build <- stuff to build the project
/project/docs <- docs for the project
/project/sources
/project/sources/c++ <- c++ source files
/project/sources/bindings <- the bindings that'll wrap c++ for python using something as boost:python
/project/sources/python <- this is the source folder to be specified in pydev
If you do decide to go with eclipse links, just make sure you only use links before the source folder level (pydev won't recognize eclipse links inside a source folder).
As for .svn, you should be able to right click the project > team > share project (but that has nothing to do with pydev).
Cheers,
Fabio
Dear Fabio,
Thanks! That sounds like a sensible way of doing it. I will try that.
Jakob