Re: [Dev-C++] CodeBlocks

[Daniel K. O. <dan...@ya...>]

Per Westermark wrote:

>But that isn't really a problem. You can find out the needed
>configurations yourself and specify in the project.
>  
>
Of course, I can always paste this

-IC:/MINGW/include/gtk-2.0 -IC:/MINGW/lib/gtk-2.0/include 
-IC:/MINGW/include/atk-1.0 -IC:/MINGW/include/pango-1.0 
-IC:/MINGW/include/glib-2.0 -IC:/MINGW/lib/glib-2.0/include

and this

-LC:/MINGW/lib -lgtk-win32-2.0 -lgdk-win32-2.0 -latk-1.0 
-lgdk_pixbuf-2.0 -lpangowin32-1.0 -lgdi32 -lpango-1.0 -lgobject-2.0 
-lgmodule-2.0 -lglib-2.0 -lintl -liconv

whenever I need to write a quick GTK+ app. But it's obviously tiresome. 
I have ~40 .pc files, I use pkg-config a lot - I even create some .pc 
files for some setups I use often.
Maybe for just a single big project it isn't a burden, but if you just 
want to write a small prototype, a test case, etc, it's really inconvenient.


>While it is nice to have the project dynamically auto-adjust itself
>whenever the gtk libraries are rebuilt with other options, it is not a
>show stopper to do it manually...
>  
>
And it's nice to have an IDE that was supposed to speed up the work, but 
it's not a show stopper to code and invoke all the MinGW binaries in a 
shell by hand. IMHO IDEs are all about usability; instead of making the 
IDE recognize all the options for different compilers, the developers 
should be more concerned about making a confortable environment for the 
programmers (the "Project's Build Options" window is a total mess, and 
there are too many entries in the main menu).


Code::Blocks is much superior to (R.I.P.) Dev-C++, but those little 
annoyances still make me use more Dev-C++ than Code::Blocks (yes, I use 
both).


---
Daniel K. O.


	

	
		
_______________________________________________________ 
Yahoo! Acesso Grátis: Internet rápida e grátis. 
Instale o discador agora!
http://br.acesso.yahoo.com/