Code::Blocks Forums

User forums => Help => Topic started by: H on February 08, 2010, 05:50:12 pm

Title: Opening Code Blocks project file (.cbp) in Visual Studio 2008
Post by: H on February 08, 2010, 05:50:12 pm
I'm switching over to Visual Studio 2008 from Code Blocks. I have a project written in Code Blocks, and I'd like to manage it in Visual Studio. The problem is that the project file for the program is in the .cbp file format. Is there any way to get this working in Visual Studio?
Title: Re: Opening Code Blocks project file (.cbp) in Visual Studio 2008
Post by: MortenMacFly on February 08, 2010, 05:59:36 pm
Is there any way to get this working in Visual Studio?
It's probably better to ask the devs of VS. C::B does not support any other than C::B itself. Import is another story.
Title: Re: Opening Code Blocks project file (.cbp) in Visual Studio 2008
Post by: stahta01 on February 08, 2010, 09:32:39 pm
If you wish to support BOTH Visual Studio and Code::Blocks projects;
I suggest looking into preMake or CMake build programs.

http://premake.sourceforge.net/
http://www.cmake.org/

Tim S.
Title: Re: Opening Code Blocks project file (.cbp) in Visual Studio 2008
Post by: starkos on February 11, 2010, 08:53:49 pm
The URL for Premake is actually http://industriousone.com/premake (http://industriousone.com/premake). Feel free to contact me if you have any questions about it.
Title: Re: Opening Code Blocks project file (.cbp) in Visual Studio 2008
Post by: TerryP on February 13, 2010, 07:56:18 pm
If you're moving the project from C::B to VS, just note down the settings from the Code::Blocks projects and create an equivalent solution in Visual Studio. Depending on your familiarity with, and ease of reading them, you may find it faster to open your .cbp files in Visual Studios text editor rather then running both IDEs side by side. Like .vcproj files, .cbp are just XML files, and are fairly straight forward to read/edit. The biggest issue you'll have to worry about, is if you're transitioning from GCC to Visual C++ for the compiler as well - option flags in one tool suite, do not always line up with the other.


In my personal experience, CMake is very overrated, but can be handy if you wish to support multiple IDEs.