User forums > Using Code::Blocks
Em::Blocks has forked into EmBlitz
stahta01:
I like Em::Blocks licensing web page.
http://www.emblocks.org/web/licensing-main
Tim S.
oBFusCATed:
--- Quote from: vdaniel on March 06, 2014, 10:15:49 am ---Is it possible in Code::Blocks IDE to create a new toolbar or edit the existing?
--- End quote ---
The only way to create a toolbar at the moment it to write a custom plugin, sorry.
I've it on the todo to implement a scriptable toolbar creation, but I've no time for it at the moment.
ollydbg:
--- Quote from: stahta01 on March 06, 2014, 05:50:52 pm ---I like Em::Blocks licensing web page.
http://www.emblocks.org/web/licensing-main
Tim S.
--- End quote ---
It has some text mention Codeblocks: http://www.emblocks.org/web/77-homepage/8-history
--- Quote ---
History
It all started with the use of Code::Blocks as an IDE for embedded software development as a replacement for other Java written tools which were too slow or unstable.
Impressed by the Scintilla editor capabilities there was a growing wish for more embedded related features instead of the Desktop oriented approach.
Instead of all those options like e.g. a resource compiler or dynamic library builds, we need options for assembler tools and static library buildings. The linker for embedded tools often need more specific information like device type, heap/stack space or linker script settings. And if those features are there then it is also tempting to make it more universal instead of the GCC flavor of Code::Blocks. By supporting all kind of compiler tools the IDE will become a multi target solution.
So the rewriting of Code::Blocks started and the changes needed were so significant that they could only be realized in a forked source base. Once rewriting a lot of code, in all kind of places, Em::Blocks now really supports multiple targets within one project with assembler highlighting for the target in scope. There are dedicated options for assembler and linker tools and the project manager is fully optimized to embedded software design.
By forking Code::Blocks there is one big advantage, both IDE's can by used side-by-side without conflicting errors.
--- End quote ---
But his license is not correct: http://www.emblocks.org/web/licensing-main
--- Quote ---Application GPLV3 SVN
SDK LGPLV3 SVN
--- End quote ---
Our SDK is not LGPLV3, it is GPLv3, but as exception rule to allow closed source plugin to link to it.
scarphin:
--- Quote from: ollydbg on March 07, 2014, 01:38:04 am ---Instead of all those options like e.g. a resource compiler or dynamic library builds, we need options for assembler tools and static library buildings.
--- End quote ---
I too think assembler tools are important for the embedded developer. It would be really nice if cb inherited assembler features from em::blocks. ;)
stahta01:
--- Quote from: scarphin on March 07, 2014, 04:08:08 am ---
--- Quote from: ollydbg on March 07, 2014, 01:38:04 am ---Instead of all those options like e.g. a resource compiler or dynamic library builds, we need options for assembler tools and static library buildings.
--- End quote ---
I too think assembler tools are important for the embedded developer. It would be really nice if cb inherited assembler features from em::blocks. ;)
--- End quote ---
I just spent the last 4 hours trying to build em::blocks; no success.
I am thinking that he/she created a custom wxWidgets library or a lot of source code is not in the SVN needed to build it.
(I am leaning towards both things being true.)
I never found the source code for the assembler features, or even the compiler/debugger code.
Tim S.
Navigation
[0] Message Index
[#] Next page
Go to full version