andrewducker (
andrewducker) wrote2008-04-27 09:45 am
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Things that annoy me about Visual Studio #1
The solution at work has 11 projects in it.
Even if the compilation on the very first project fails, it continues to compile all of the other ones.
Why, oh why, would I want to compile projects that are dependent on one that failed to compile?
Even if the compilation on the very first project fails, it continues to compile all of the other ones.
Why, oh why, would I want to compile projects that are dependent on one that failed to compile?
no subject
no subject
At some point, you likely need nAnt or the like to really do the job right. W0onder if Maven's been ported?
no subject
no subject
no subject
Although if I wanted to do it the Unix way I could write my own build scripts - which would work just fine.
no subject
Handwriting makefiles has always seemed about as easy as managing projects with an IDDE, the only difference being you have to actually type them in.
I'm not going to mention the existence of autoconf, autoproj et al because, frankly, I'm ashamed that such a system has become the 'standard' for Unix applications. When the best thing I can think to say about a system is 'Well, at least you don't have to hand-edit XML', you know I'm struggling. I'd still rather use autoconf than a build system that makes me type XML, though. It's a political thing.
Actually, the best thing about autoconf is that it works. The second best thing is that you don't have to type XML. The third best thing about it is that you don't have to type it at all if you use Anjuta to build the scripts for you...
no subject