<div class="gmail_quote">On Mon, Nov 29, 2010 at 7:28 PM, Andreas Pakulat <span dir="ltr"><<a href="mailto:apaku@gmx.de">apaku@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 29.11.10 19:00:13, Syron wrote:<br>
> 2010/11/29 Michael Hart <<a href="mailto:michael.george.hart@gmail.com">michael.george.hart@gmail.com</a>>:<br>
> > Being a very senior and experienced C++ developer for the most part all I<br>
> > ever cared about was the C++ language and the various APIs I used in getting<br>
> > an application to market. So what may seem appalling to you, I can only make<br>
> > the assumption I was using automake as my build tool.<br>
><br>
> I think it's strange that you're a senior developer and have never<br>
> dealt with any build system - understanding how build systems work is<br>
> an important thing, that's what I learned as soon as I wrote my first<br>
> project with more than one file. And I am also worried about the fact<br>
> that you have 300 C++ files in _one_ directory, that seems like a big<br>
> mess.<br>
> If you spend some time learning a build system (qMake, CMake,<br>
> whatever), you will soon learn how powerful they are.<br>
<br>
</div>Well, if you're always only targetting Windows you can easily get around<br>
without knowing any buildsystem if you stick to VS for building your<br>
app. Though at some point for larger or legacy projects you will get to<br>
dive into the various options that VS offers for customization. At least<br>
I think you can. But then again, VS uses a much more constrained<br>
buildsystem and is not as capable as CMake (leaving aside the<br>
missing cross-platform support).<br>
<br>
Or you have someone in the team that cares about the buildsystem-stuff<br>
and all the C++ developers ever have to care about is adding the files<br>
at the right place. Thats how it works with KDevelop for example, there<br>
are one or two persons with in-depth cmake knowledge that handle all the<br>
harder stuff. The rest of the team mostly just add the files in the<br>
right cmake-files.<br>
<br>
That being said, IMHO it KDevelop should be able to handle<br>
adding/deleting files via its existing cmake-change-wizard. All thats<br>
really needed is a hook when files are being added to the project. I<br>
actually thought this was already done for 4.1, but maybe it gets in for<br>
4.2??<br>
<br>
Andreas<br>
<font color="#888888"><br>
--<br>
You don't become a failure until you're satisfied with being one.<br>
</font><div><div></div><div class="h5"><br>
--<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
</div></div></blockquote></div><br><div>We can do most of that already, we're just missing the add_library/executable wizard. That should be fairly easy to add, though.</div><div><br></div><div>Aleix</div>