I would very much appreciate being able to compile on my Linux box using Code::Blocks from my XP desktop. Currently, I edit my files on the XP box via samba and open a console to the Linux box to invoke a makefile by hand, which is a nuisance (admitted, I could install wxGTK and just compile C::B for Linux, but installing wxGTK is a nuisance, too, and the X servers for Windows aren't great, either).
I started to write some code but it turns out that I gotta modify some core functionalities, XML project file format, FileOpen dialog, etc. My question is, would you incorporate my code intro the CB ?.
Can't you pack the functionality into a plugin? This would cause a lot less trouble both for you and for the devs.
What if the user edits sources on a SMB volume, that way the sources are on the Linux box already. Then you make a modified compilergcc "compile remotely" plugin which does some network wizardry (use
plink or
rsh to connect to the Linux box and invoke gcc with the parameters that you get from the project).
This would require zero changes to the application, and would probably not be an awful lot of work, either. The compilergcc plugin already exists and works reliably, all you need to do is call
plink instead of running
mingw-gcc directly. Then you need one extra configuration screen, and it should do.
I ask this because with the new functionalities/ bug fixes added everyday, it will be a pain in the ass to report each time my modifications into the main trunk.
Is this not just what
cvs update does? You can update regularly while making changes, and the modifications to the main trunk will be merged to your working copy. And when you have reached a point where you want to release your changes, you make a patch against the current release. Does that not work out?