Author Topic: Where is output/Codeblocks and devel/Codeblocks  (Read 6443 times)

Offline sarun

  • Multiple posting newcomer
  • *
  • Posts: 14
Where is output/Codeblocks and devel/Codeblocks
« on: February 02, 2012, 03:55:32 pm »
from file BUILD in SVN checkout revision 7746
Quote
Working on Code::Blocks sources from within Code::Blocks!
---------------------------------------------------------
The following apply for all platforms where you have Code::Blocks installed and working.

These two folders will contain the same files and directory structure and you can use the IDE from either of these two directories. This structure has been created so that you can work in Code::Blocks while editing Code::Blocks' sources ;).
Basically, you 'll be using the "output/CodeBlocks.exe" executable. Code::Blocks' project settings are such that all output goes under "devel". So you can edit Code::Blocks' sources inside Code::Blocks and, when pressing "Run", it will run the "devel/CodeBlocks.exe" executable ;). This way, you can't ruin the main executable you 're using (under "output"). When your changes satisfy you and all works well, quit Code::Blocks, run "make update" from command line and re-launch "output/CodeBlocks.exe". You 'll be working on your brand new IDE!

I've just successfully compile and install SNV build of Code::Blocks and I'd like to start looking through its source. But I can't find two directories mentioned above, the only thing I've found is Code::Blocks executable in installation directory (/usr/local/bin). Then, where can I find the sources?

(I'm using Ubuntu 11.10)

Thanks.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13406
    • Travis build status
Re: Where is output/Codeblocks and devel/Codeblocks
« Reply #1 on: February 02, 2012, 03:57:33 pm »
In order to have these two directories, you need to build c::b from inside c::b and the you have to run ./update in src/
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline sarun

  • Multiple posting newcomer
  • *
  • Posts: 14
Re: Where is output/Codeblocks and devel/Codeblocks
« Reply #2 on: February 02, 2012, 04:09:39 pm »
Thanks for you really fast reply,

but when I tried to compile Code::Blocks inside Code::Blocks, I got this :
Quote
-------------- Build: tinyXML in Code::Blocks ---------------

Compiling: base/tinyxml/tinyxmlerror.cpp
cc1plus: error: unrecognized command line option ‘-mthreads’
Process terminated with status 1 (0 minutes, 0 seconds)
0 errors, 0 warnings (0 minutes, 0 seconds)
 

How can I fix it?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13406
    • Travis build status
Re: Where is output/Codeblocks and devel/Codeblocks
« Reply #3 on: February 02, 2012, 04:25:22 pm »
Open the -unix.cbp file.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline sarun

  • Multiple posting newcomer
  • *
  • Posts: 14
Re: Where is output/Codeblocks and devel/Codeblocks
« Reply #4 on: February 02, 2012, 04:48:16 pm »
Thanks again.

One more question, why the GUI of the build via Code::Blocks and via make install are different, for example, the menu bar, in make install version has the "Tools+" menu but Code::Blocks version not and why the make install version always ask for spell checker configuration?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13406
    • Travis build status
Re: Where is output/Codeblocks and devel/Codeblocks
« Reply #5 on: February 02, 2012, 04:59:49 pm »
Build the Contribplugins-unix.workspace and they will be the same.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline sarun

  • Multiple posting newcomer
  • *
  • Posts: 14
Re: Where is output/Codeblocks and devel/Codeblocks
« Reply #6 on: February 02, 2012, 05:44:05 pm »
Thanks, and I'll start to understand the code.