<div dir="ltr"><br><br><div class="gmail_quote">On Tue, Jul 22, 2008 at 6:12 AM, Matt Rogers <<a href="mailto:mattr@kde.org">mattr@kde.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><br><div><div class="Ih2E3d"><div>On Jul 21, 2008, at 12:39 PM, Aleix wrote:</div><br><blockquote type="cite"><div dir="ltr">If you think this is the correct way to work i'll commit it<br><br></div></blockquote>
<div><br></div></div><div>Not that this is of any concern for those of us with CMake, but what about handling automake or standard Makefile projects with this? In most cases, automake is 'make check' and the standard Makefile projects could use whatever they want. What about ant, should somebody step up with support for that?</div>
</div></div></blockquote><div> </div><div>Umm.. This is all about giving more information for each target. If the buildtool provides it, then cool if not, then we just use ProjectTargetItem as we did before. Actually everything keeps compiling and working (that I know of) at the moment, without any changes.<br>
<br>Now we could have a different icon for each item. Any idea for it?<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style="">
<div><div><br></div><div>Just curious.</div><div>--</div><div>Matt</div><br><blockquote type="cite"><div><div></div><div class="Wj3C7c"><div dir="ltr"><div class="gmail_quote">On Fri, Jul 18, 2008 at 8:46 PM, Aleix <<a href="mailto:aleixpol@gmail.com" target="_blank">aleixpol@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div dir="ltr">Yes, I will add it when someone gives a logical way to do it.<br><br>We were discussing about it but we didn't sort it out.<br>
<br>What do you think about a bool ProjectTargetItem::isTest() method?<br><br> Bye,<br><font color="#888888">Aleix</font><div><div></div><div><br><br><div class="gmail_quote">On Fri, Jul 18, 2008 at 3:43 PM, Manuel Breugelmans <<a href="mailto:mbr.nxi@gmail.com" target="_blank">mbr.nxi@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div>On Monday 16 June 2008 22:54:40 Aleix wrote:<br> </div><div>> On Mon, Jun 16, 2008 at 10:38 PM, Manuel Breugelmans <<a href="mailto:mbr.nxi@gmail.com" target="_blank">mbr.nxi@gmail.com</a>><br>
><br> > wrote:<br> > > A couple of weeks ago it was suggested to provide test executable<br> > > location from the buildtool. While this is not doable for all builders<br> > > (and surely not<br> > > for all test frameworks) its the route to go for the qtest+cmake<br>
> > combination.<br> > ><br> > > Unless I overlooked it's not yet implemented. Does anyone plan to? If not<br> > > I could probably do it, with a bit of directions. Maybe subclass a<br> > > ProjectTargetItem with a ProjectTestTargetItem?<br>
><br> > There is no API at the moment for that, I can do it if you want to (if you<br> > can wait for me to finish exams)...<br> ><br> > By do it I mean add the API and implement it to cmake.<br> <br> </div>
Do you still plan to add this? I've done a quick ``find 'CmakeLists.txt' | grep<br> "kde4_add_unit_test" '' parser a couple of weeks ago but obviously prefer not<br> to use it.<br> <font color="#888888"><br>
<br> Manuel<br> </font><div><div></div><div><br> > Aleix<br> ><br> > > Manuel<br> > ><br> <br> <br> <br> _______________________________________________<br> KDevelop-devel mailing list<br> <a href="mailto:KDevelop-devel@kdevelop.org" target="_blank">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></div></div> </blockquote>
</div><br></div> </div></div><span><cmake_targets.patch></span><span><targettype.patch></span>_______________________________________________<div class="Ih2E3d"><br>KDevelop-devel mailing list<br><a href="mailto:KDevelop-devel@kdevelop.org" target="_blank">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></blockquote></div><font color="#888888"><br><div> <span style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><div style="">
<span style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><div style="">
<div>Matt</div></div></span></div></span> </div><br></font></div><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>
<br></blockquote></div><br></div>