Re: [Mingw-users] Noob issue: MinGW / CodeBlocks

[Peter R. <p.r...@sh...>]

On 07/11/10 07:21, Tor Lillqvist wrote:
> (Adding the list back to Cc:)
>
>> Good question.  I'm working with the initial install.
> Why not start by learning to compile a Hello World -style program
> using just the command line? It isn't rocket science. I think your
> mail was a great example of how an IDE that is supposed to make a task
> easier actually makes it a lot more complicated.
>
> Assuming you have your helloworld.c file, then compiling it with MinGW
> is as simple as going to that folder in a command interpreter
> (cmd.exe) window (or a MSYS shell window) and entering the command:
> "gcc -Wall -o helloworld.exe helloworld.c" (without the quotes).
>
> Let's break apart that command: "gcc" is the name of the compiler
> program. "-o helloworld.exe" tells what the resulting executable file
> should be called. And "helloworld.c" is the name of your source file.
>
> Now, once it gets more complicated and you have several source files,
> perhaps some libraries etc, you learn to add those one thing at a
> time. And obviously you don't want to be typing the same command
> manually over and over. So use a batch file, a shell script, or a
> Makefile. Or... try to make CodeBlocks do it. If you know the basics
> of command-line usage, maybe you can find the relevant settings in
> CodeBlocks that are unnecessary to you and cause problems and see what
> command-line options they correspond to, and clean such cruft away.
>
> --tml
>
Clearly some discussion off-list...

To give a counter-view: My advice - Persist with CodeBlocks which works 
beautifully with MinGW. Some people prefer the command line interface. 
Some (like me!) cannot comprehend why anybody would use the CLI when 
IDEs like CodeBlocks exists.

I suggest you try both and go with the method you find easiest/most 
convenient/most productive for your projects.


P