User forums > Using Code::Blocks
Code::Blocks command line requires to export DISPLAY
Jenna:
It's not an easy task to change this, because of the use of wxwidgets-classes that are not in wxbase.
I just created a patch that makes it work (only tested on linux), but it was/is an ugly hack with tons of ifdefs and nearly not to maintain.
Splitting C::B in a gui- and a non-gui-part is a really hard job, even if it would be good to have it.
It's still in my mind, but there are so many other things to do.
zabzonk:
> How do you make CodeBlocks use an X server on the windows host ?
Set the DISPLAY variable on the Linux box to the IP address or name of the Windows box running the X server.
> The windows version of CodeBlocks uses Windows display, how do you change that ?
I wasn't suggesting you do that - I suggested you allowed the Linux CB instance to use the Windows display via an X server.
> All the X servers that I've seen on Windows allow you to get the remote display of a linux/unix machine.
It actually works the other way round - the X client (i.e CB) on the Linux box uses the Windows X server.
LittleJawa:
--- Quote from: zabzonk on October 27, 2009, 01:21:47 pm ---> How do you make CodeBlocks use an X server on the windows host ?
Set the DISPLAY variable on the Linux box to the IP address or name of the Windows box running the X server.
> The windows version of CodeBlocks uses Windows display, how do you change that ?
I wasn't suggesting you do that - I suggested you allowed the Linux CB instance to use the Windows display via an X server.
> All the X servers that I've seen on Windows allow you to get the remote display of a linux/unix machine.
It actually works the other way round - the X client (i.e CB) on the Linux box uses the Windows X server.
--- End quote ---
Well... Ok, but that is already solved. I'm using Xvfb on the linux box. This is a "fake" X server. I just redirect the linux box's DISPLAY to it, and CodeBlocks is fine.
My problem here is that the Windows version of CodeBlocks hangs when I run it from a service (typically: a build software).
This makes unattended builds on the WINDOWS host impossible to make...
And I can't redirect the windows' display to anything else, as far as I can tell.
Thanks for the suggestion anyway.
LittleJawa:
--- Quote from: jens on October 27, 2009, 01:03:08 pm ---It's not an easy task to change this, because of the use of wxwidgets-classes that are not in wxbase.
I just created a patch that makes it work (only tested on linux), but it was/is an ugly hack with tons of ifdefs and nearly not to maintain.
Splitting C::B in a gui- and a non-gui-part is a really hard job, even if it would be good to have it.
It's still in my mind, but there are so many other things to do.
--- End quote ---
Well... I had a look at CodeBlocks' code and came to the same conclusion : lot of work, and probably not something that I could try by myself since I know nothing on CodeBlocks internals :-(
I just hoped someone would have found a workaround on this, or could come with a great idea that I did not already have...
Could you provide me your patch, just so that I can try it on Windows ?
I understand it should not make it to your development's trunk, but if it can solve my problem today, it would at least buy me some time to find another workaround...
MortenMacFly:
--- Quote from: LittleJawa on October 27, 2009, 01:33:54 pm ---I understand it should not make it to your development's trunk, but if it can solve my problem today, it would at least buy me some time to find another workaround...
--- End quote ---
Notice that this patch solves the "issue" (it's not really an issue though for an IDE) that Code::Blocks needs an X-Server, e.g. when run remotely. It does not solve the issue if the app you are developing needs an X-Server to run. Which is IMHO the case for you.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version