Hey,
On Wed, Dec 18, 2013 at 2:32 AM, Keith Curtis <keit...@gmail.com> wrote: > I don't even know the names of the various modules I'm working in and > prefer to let the smart system figure it out ;-) make build-nocheck works > great and things run so much faster on my little laptop. Thank you. I put > this info in the wiki to save questions in the future. > Please don't. There are good reasons we don't document building without the tests. We had some problems in the past and normally force every developer to execute the minimum amount of tests during a full build. While working on some parts of the code you normally only rebuild this part which limits the number of executed tests. Regards, Markus > -Keith > > > On Mon, Dec 16, 2013 at 1:33 AM, Khaled Hosny <khaledho...@eglug.org>wrote: > >> On Mon, Dec 16, 2013 at 12:56:59AM -0500, Keith Curtis wrote: >> > It appears when making changes to individual C++ files that my computer >> > spends about 90% of the build time running unit tests. >> >> It seems that ‘make foo.build’ will not run the tests, at least this is >> what I “discovered” few days ago. >> > > > _______________________________________________ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice > >
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
