User forums > Using Code::Blocks

how to use code blocks

<< < (2/2)

BlueHazzard:

--- Quote ---However, he cannot not spend a single hour to document it
--- End quote ---
The code is documentation ;) Writing good documentation needs as much time as coding (if not more) and is a tedious process especially if it is not your native language...

What do you need documentation for?
File->New
Project->Build options->Compiler Settings->Compiler flags
Project->Build options->Pre/post build options
ecc...
This are all self explanatory names... Writing documentation for this is not necessary. As soon as you need this options you are experienced with the build process to know where to search. The experience comes with try and error....


--- Quote --- If no one can understand how the entire program works, then how can you find any volunteer programmers willing to improve the software.  Before any programmer can start tweeking a program, he better know how to use the entire program first.

--- End quote ---
There are 100.000 weekly downloads and this forum is not crowded over with people who question the simple menu things, so this does not seem to be a problem....


However, i am not here to discuss this, the time for this discussion is simply wasted and it would be better to spend it to write documentation. There is not much documentation, this is a sad fact. The devs have not much time do write it. If you have the time we all would be happy if you could help. If you have a question i am happy to answer and help, but i will not discuss this future....

greetings

exchg:

--- Quote from: biotech54 on May 20, 2017, 01:28:42 am ---However, programmers who are new to using a C++ IDE are lost.

--- End quote ---
IDE it is just GUI representation of common processes/commands for compiler/linker command line (except some text editor advantages).
IDE project file it is just some automation (batch of common commands and flags) for compiler.
So maybe this programmers(which are lost) better to learn how the compiler works first?
It's just philosophical reasoning ))

oBFusCATed:

--- Quote from: biotech54 on May 19, 2017, 09:58:52 pm ---I can't even figure out the simplest thing -
 how to create different versions of a program using codeblocks, so that i can test out each version separately.

--- End quote ---
1. create multiple targets that build separate executables
2. create a single target and add some command line arguments and some dispatching to different function in the main function
3. create separate projects and organize them in a workspace
4. use something like cmake to do similar things

Last time I've looked at the manual it had explanation for projects, targets and workspaces. Isn't this still the case?

gd_on:
And what about http://www.codeblocks.org/user-manual even if it's outdated ?

gd_on

Navigation

[0] Message Index

[*] Previous page