I know, the question has already been asked but the answer doesn't meet my requirements.
So is there is any way to import a Visual Studio project with all its parameters in Eclipse CDT ? If yes, how could I do that ?
If you want to know more details about my situation, there it is :
I am joining a rather big collaborative C++ project, with a complex repository and many sub-projects. Each of these sub-projects was initially developed with Visual Studio, and the parameters of the build chain are stored in a vcproj file.
Yet, I strongly resent the use of Visual Studio, am more efficient with Eclipse CDT, and don't have access to a Windows machine, so I would be really happy to not loose weeks in order to understand the whole building process...
With the risk of being a detracted answer from your question, I believe that the solution is NOT to convert a vcproj to an EClipse CDT project. You should use a better build toolchain (e. g. CMake). Once such a toolchain is in place, you can create a Visual Studio project, an EClipse CDT project, a QtCreator project, a XCode project, .
The easiest way to open a VCPROJ file, or any kind of file, is to use a universal file viewer like File Magic (Download). You can use it to open many different file formats. If it’s not compatible, the file will just open in binary.
I think you're asking the wrong question. As you've found, the .vcproj describes the build process (in addition to the list of files), and that strongly depends on the MS compiler toolchain being available.
I want to import the existing source code into Eclipse, creating a managed project, i.e. a project where makefiles are automatically generated and maintained by Eclipse. Run / Run Configurations… The project is created under an Eclipse configuration named Default. You can create several configurations: one for debugging, one for releasing, etc.
With the risk of being a detracted answer from your question, I believe that the solution is NOT to convert a vcproj to an EClipse CDT project. You should use a better build toolchain (e.g. CMake). Once such a toolchain is in place, you can create a Visual Studio project, an EClipse CDT project, a QtCreator project, a XCode project, ... from the same build configuration files.
That way, when the next IDE for C++ comes along, nobody will be wasting their time converting project files.
I think you're asking the wrong question. As you've found, the .vcproj describes the build process (in addition to the list of files), and that strongly depends on the MS compiler toolchain being available.
A better alternative (though harder to implement late in the lifetime of a project) is to use free tools such as Premake and JamPlus (just to name a few) to decouple the list of files from the build process. This is especially useful for multiplatform projects, as each developer can use their preferred editor and toolchain to contribute to the project.
That being said, I do believe Visual Studio can run under Wine... ;)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With