<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">Hello!<br> <br> On 12/6/2016 10:44 AM, Jan Iversen wrote:<br> </div> <blockquote cite="mid:825ABA9F-554E-474C-B692-C525B73C7F4E@documentfoundation.org" type="cite"> <div><br class=""> <blockquote type="cite" class=""> <div class=""> <div class="">Well, Python/Java are ~7% of LOC in LibreOffice core repo, and less then 2%(?)<br class=""> of the shipped core product.<br class=""> </div> </div> </blockquote> <div><br class=""> </div> But if I want to make an executable within the IDE,</div> </blockquote> <br> No, that's not true. To make the executable within the IDE, the project file only needs to know the correct command to launch. That command is "make".<br> <br> <blockquote cite="mid:825ABA9F-554E-474C-B692-C525B73C7F4E@documentfoundation.org" type="cite"> <div>or debug e.g. some of the unit test I still need it.</div> </blockquote> <br> Well, possibly *some* tests.<br> <br> <blockquote cite="mid:825ABA9F-554E-474C-B692-C525B73C7F4E@documentfoundation.org" type="cite"> <div>One of the hard points for new people is actually to be able to debug unit tests.</div> </blockquote> <br> Currently, new people will be unable to debug a tiny amount of tests that really require Python/Java. Wast majority don't require that.<br> <br class=""> <blockquote cite="mid:825ABA9F-554E-474C-B692-C525B73C7F4E@documentfoundation.org" type="cite"> <div> <blockquote type="cite" class=""> <div class=""> <div class=""> <blockquote type="cite" class="">The simple use case, of being able to develop/build/debug within the<br class=""> IDE....especially debugging is important. setting breakpoints on the lines<br class=""> and viewing variables is what students learn todo.<br class=""> </blockquote> <br class=""> Thats already possible with existing IDE integrations. <br class=""> </div> </div> </blockquote> At least not in the Xcode integration.</div> <div><br class=""> </div> <div>for a couple of reasons (which might apply to windows as well, will test that later):</div> <div>- the debugger cannot run, it has not main executable.</div> <div>- make and Xcode puts objects in different places.</div> <div>- Also it is important to see the relationship between modules (especially when searching for symbols).</div> </blockquote> <br> Everything I write here is based on my own experience. I mainly develop under Windows, in VS 2013 IDE. And while specifically that integration cannot build within IDE, that's the smallest problem to launch the build from console.<br> <br> <blockquote cite="mid:825ABA9F-554E-474C-B692-C525B73C7F4E@documentfoundation.org" type="cite"> <div> <blockquote type="cite" class=""> <div class=""> <div class=""> <blockquote type="cite" class="">Students want to do all development within the IDE, and I do not see why it should be impossible.<br class=""> </blockquote> <br class=""> "All development within the IDE" (including breakpoints and debugging) is already<br class=""> the status quo.<br class=""> <br class=""> </div> </div> </blockquote> I might be doing something wrong, but I have until and including today, not being able to 1/ set a breakpoint 2/ press debug 3/ stop at the breakpoint, neither in windows nor in Xcode.</div> </blockquote> <br> To debug, under Windows, you need to 'make CppunitTest_XXX CPPUNITTRACE=TRUE', which launches separate VS IDE that's ready to open source files, set breaks and press "Run". The instruction to do so is emitted when a unit test is failed.<br> <br> So, IMO, there is simply <span class="st4cursor"></span>small polishment required to fix some shortcomings of specific integrations, in your case, Xcode. Overall, the new gbuildtojson made things much better. I don't believe ve need some "IDE build systems".<br> <br> <div class="moz-signature">-- <br> Best regards,<br> Mike Kaganski</div> </body> </html>