Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Building CodeBlocks source
stahta01:
--- Quote from: LETARTARE on July 22, 2013, 05:49:40 pm ---@BlueHazzard
Okay, very good job.
Maybe we could replace
--- Quote ---CFLAGS ?= -fno-keep-inline-dllexport
--- End quote ---
--- Quote ---CXXFLAGS ?= -fno-keep-inline-dllexport
--- End quote ---
by
--- Quote ---CPPFLAGS ?= -fno-keep-inline-dllexport
--- End quote ---
I checked the Makefile, but we still control ...
and add after
--- Code: ---or
mingw32-make -fmakefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 CPPFLAGS=-fno-keep-inline-dllexport
--- End code ---
Thank you again
--- End quote ---
Feel free to post that on the wxWidgets forum; it will likely be ignored.
FYI: This is NOT a CB Makefile; if you think I am wrong please say why you think it is a CB Makefile.
Tim S.
LETARTARE:
hello @stahta01
by BlueHazard
--- Quote ---i have updated the wiki a little bit. Can someone please check it?
--- End quote ---
I read the excellent work BlueHazard on WIKI.
http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Windows
where the two lines is, and I just wanted to show him a simplification.
But you're right, I should have done on the wiki !
Thanks.
sorinev:
I finally did it. 6 days later. Minor issue with the contrib plugins when trying to build the Nassi Shneiderman diagram tool/plugin - it looks I need to download AND build boost myself, then set up the global variable editor for "boost"? Other than that, it works.
Next step. Do you guys have some kind of overall system architecture view for the Code::Blocks source that generally shows how the parts/files work and flow and go together? I don't think I'll get very far just poking around in source files trying to follow things at this point in my knowledge.
ollydbg:
--- Quote from: sorinev on July 26, 2013, 10:21:40 am ---
I finally did it. 6 days later. Minor issue with the contrib plugins when trying to build the Nassi Shneiderman diagram tool/plugin - it looks I need to download AND build boost myself, then set up the global variable editor for "boost"? Other than that, it works.
--- End quote ---
Yes, that need boost library, only this plugin is depend on the boost library. I think you can download some prebuild boost library some internet, for me, I never build Nassi Shneiderman myself, I just skip building this cbp in the contributes plugins ;).
--- Quote ---Next step. Do you guys have some kind of overall system architecture view for the Code::Blocks source that generally shows how the parts/files work and flow and go together? I don't think I'll get very far just poking around in source files trying to follow things at this point in my knowledge.
--- End quote ---
I'm not sure that there are some document about this, but here I can explain all what I know:
src/src -> this contains code for building "codeblocks.exe"
src/sdk -> codeblocks.dll
src/base -> some base library needed for sdk, like tinyxml
src/include -> all the header files of sdk
plugins-> all the plugins, there are two kind of plugins, the core plugins and the contribute pluings (in a contrib subfolder)
src/devel -> all the build output (mainly binaries containing debug information)
src/output ->when you run "update.bat", it will copy from devel folder, but strip all the debug information
src/templates and src/scripts contains project wizard scripts
Is that enough? If not, just ask here.
sorinev:
--- Quote from: ollydbg on July 26, 2013, 11:29:44 am ---Yes, that need boost library, only this plugin is depend on the boost library. I think you can download some prebuild boost library some internet, for me, I never build Nassi Shneiderman myself, I just skip building this cbp in the contributes plugins ;).
--- End quote ---
Alright, since I'm trying to build everything else under the sun (wxwidgets, codeblocks, qt, getting qt5 to work with codeblocks), I may as well throw some boost building in there too. I built everything in the workspace for the sake of thoroughness, as that's just how I am. I'm probably not going to actually use 95% of that stuff, at least in the foreseeable future, but I like knowing it's there.
--- Quote from: ollydbg on July 26, 2013, 11:29:44 am ---I'm not sure that there are some document about this, but here I can explain all what I know:
src/src -> this contains code for building "codeblocks.exe"
src/sdk -> codeblocks.dll
src/base -> some base library needed for sdk, like tinyxml
src/include -> all the header files of sdk
plugins-> all the plugins, there are two kind of plugins, the core plugins and the contribute pluings (in a contrib subfolder)
src/devel -> all the build output (mainly binaries containing debug information)
src/output ->when you run "update.bat", it will copy from devel folder, but strip all the debug information
src/templates and src/scripts contains project wizard scripts
Is that enough? If not, just ask here.
--- End quote ---
Thanks, and that is indeed useful. But what I actually meant was when looking at the IDE itself, how am I going to know, filewise, where something else? For example, if I'm looking at xyz area of the IDE, which source file do I find xyz in? What I'm really looking for is some kind of structure chart, organizational chart, etc. that I can get a good overall view of everything from. Even a written tree or outline would work.
Also, I've never built such a large project before. My biggest project is a win32/c++ project that I wrote with about 11k lines. I can just put a breakpoint in it, hit F8, and that's that. Is that really possible with projects as big as codeblocks?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version