@tomazzi,
this is just my opinion. Don't want to make anyone do it, just saying.
Scripts ? But how you write them , when you never used gcc in terminal ? ( not talking about you, saw your libraries , keep up the good work man )
Thats all from me on this topic.
Best Regards
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Setting up a C programming environment
Re: Setting up a C programming environment
You don't - that's what I've already said, I think.den4oman wrote:Scripts ? But how you write them , when you never used gcc in terminal ?
For autotools, You need to write a configuration file, which is then used to generate necessary makefiles, which in turn are invoked using very well known commands: configure && make
In an IDE You just define all the project properties using GUI, and the software generates required set of gcc commands (just like in the example in my previous post.).
This doesn't mean however, that You don't have to know what particular compiler options are doing. None of the IDEs will set the options for the project - this is responsibility of the author.
Therefore, the programmer must read the documentation for the compiler and the linker.
But:
In any way this doesn't imply that You have to learn and test the options in the terminal.
Any environment can be used for learning how particular option works, and interactive terminal is definitely not the most convenient one.
Regards.
Odi profanum vulgus