Re: Build without doing any tests?

Taking it a stage further, I would like to have assert options for attended and unattended operation, with builds defaulting to unattended. It can be useful to run regression tests with assertions enabled, but logging assertion failures rather than displaying a dialog. Obviously, that depends

Re: Build without doing any tests?

If it's OSL_ASSERT, it's probably the non product build story, though I am not sure why that's bringing up dialogs at compile time. Maybe the Google Tests are working too well: they initialize sal, so failures in OSL_ASSERT (as opposed to in the Google Test APIs) could be bringing up dialogs just

Re: Build without doing any tests?

It looks as though the attached .pdf image did not get through. Here is the data from it: The error was in main/sal/osl/w32/process.cxx, line 340, null message. The assertion is "OSL_ASSERT(g_command_args.m_nCount > 0);" On 3/13/2016 10:44 AM, Patricia Shanahan wrote: Hi Damjan, I got

Re: Build without doing any tests?

Hi Damjan, I got another one. This is a cygwin build on Windows 8.1. I'll leave it alone for a bit in case there is more information I should capture. It may be possible to attach a debugger to the process. Here are the last few lines from the build output: Creating library

Re: Build without doing any tests?

Will do. It will help if I am fully awake when dealing with it, not first thing on daylight savings time morning. I need to do an svn-update and rebuild soon. On 3/13/2016 10:01 AM, Damjan Jovanovic wrote: It is highly unusual to get a dialog during build. Please send a screenshot next time.

Re: Build without doing any tests?

It is highly unusual to get a dialog during build. Please send a screenshot next time. "./configure --help" is probably the best - I couldn't find anything better so far. On Sun, Mar 13, 2016 at 6:19 PM, Patricia Shanahan wrote: > I also have no idea which tests - I just know I

Re: Build without doing any tests?

I also have no idea which tests - I just know I was greeted this morning by an incomplete build and the form of AOO dialog I only see from a debug build. The build resumed as soon as I answered the dialog. I'll try --disable-unit-tests next time I start a build. Is there a general document

Re: Build without doing any tests?

I am not sure which tests you are talking about and at what stage of the build process they occur. The Google Test unit tests don't bring up dialogs AFAIK, but can be disabled by passing --disable-unit-tests to ./configure. If this happens after starting AOO then see