User forums > Using Code::Blocks
Team cross-platform development with Code::Blocks?
rickg22:
Hi everyone... I know it's embarrassing for a C::B dev to ask this :oops:, but...
How do you do cross-platform developing with C::B when one of the developers uses Windows and another uses GNU/Linux?
I have this project ( http://sayavideoeditor.sourceforge.net/ for the curious - volunteers welcome ;-) ) that I started in GNU/Linux, so the project build settings are linux-specific of course. So, what should my Windows teammate do so he's able to compile our application with C::B?
Should I keep two separate .cbps? And how to sync them efficiently whenever I add new files to the project?
Yiannis, what did you do with C::B to solve this problem? I never needed to ask.
Sincerely,
your friendly ex-dev Rick ;-)
mandrav:
--- Quote ---Yiannis, what did you do with C::B to solve this problem? I never needed to ask.
--- End quote ---
Well, for various reasons, we keep two separate .cbp files. But this obviously is a hassle (to keep in sync etc). One of the reasons is that when I started writing C::B (yes, alone at the start :)) there was no script generation tool to generate C::B project files, obviously :lol:.
Anyway, things have changed since those times and now there are at least a couple of such tools that support C::B project files generation.
I think CMake supports it albeit partially: it generates a normal Makefile and creates a C::B project that uses this Makefile. Not the best of options but one certainly worth considering :).
Of course, things could very well have changed on this front since I last checked it out. If someone knows more about this, please share.
The tool that I 've found supports C::B almost fully and generates native C::B projects is Premake (pick version 3.6, don't go for the 4.x branch). I have first hand experience with this tool and I use it for many other projects of mine. I would definitely recommend this :).
Now wait for anyone else having pearls of wisdom to share... :)
rickg22:
Still no help.... :(
Hey how about this: A feature called "Import files from another project" so that the files and targets get added, but the project build options remain the same?
Can it be done?
Deschamps:
Maybe I haven't understand the question, but... Why don't simply define different build targets (for windows and Linux platforms) using the same .cbp? Even (depending of your project), if you are developing wxWidgets apps and the developers using Windows can use the wx-config port, then maybe you could use exactly the same target (and the same files, therefore) in both platforms.
Regards.
JGM:
Also virtual targets may help organize, one virtual target for windows and other for unix systems. And inside each virtual target the release and debug versions of each platforms.
Navigation
[0] Message Index
[#] Next page
Go to full version