On Sun, Jul 14, 2019 at 07:58:46AM +0200, Kornel Benko wrote: > Am Sonntag, 14. Juli 2019, 01:17:57 CEST schrieb Jean-Marc Lasgouttes: > > Le 14/07/2019 à 00:15, Kornel Benko a écrit : > > > Am Samstag, 13. Juli 2019, 23:13:50 CEST schrieb Jean-Marc Lasgouttes: > > >> Le 13/07/2019 à 23:01, Kornel Benko a écrit : > > >>> At least the message should be easy identifiable as error, so that > > >>> we can parse it while testing layouts. > > >> > > >> Can you tell me more about how this works? I did not try the cmake side > > >> of things. From what I read, you parse the stderr output and assume an > > >> error if the string Error appears. > > > > > > That is the problem ... the process ends without error. > > > But we could parse the output and fake an error for the test-run. > > > > > >> What would be the place of a Warning in this setting? > > > > > > It would serve as a string to be parsed by the test-machinery. > > > (The parsing is not there yet, but is not difficult to create) > > > > In check_layout.cmake, I see this: > > > > if (_err MATCHES "Error reading") > > message(STATUS "_err = \"${_err}\"") > > message(FATAL_ERROR "Errors found") > > endif() > > > > Isn't this some kind of parsing? > > > > JMarc > > Yes, exactly.
Is there anything left to be done for this? Scott
signature.asc
Description: PGP signature
-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel