[PATCH weston v3 1/5] Expanded unit test framework to cover base requirements.

Peter Hutterer peter.hutterer at who-t.net
Mon Jun 8 22:15:52 PDT 2015


On Thu, Jun 04, 2015 at 12:50:47AM -0700, Jon A. Cruz wrote:
> On 06/03/2015 10:15 PM, Peter Hutterer wrote:
> > On Tue, May 26, 2015 at 04:06:37PM -0700, Jon A. Cruz wrote:
> >> Added simple unit/integration test framework and corresponding
> >> test program.
> >>
> >> Added a simple C-based test framework and an example program
> >> that uses it to run through some simple wayland client checks.
> > 
> > what does the Z in zuc stand for? zimple? :)
> > 
> 
> Oooh, that's good. Might go with it.
> 
> Originally it was 'letter that is more unlikely to already be in use and
> collide'
> 

[...]

> >>  
> >>  BUILT_SOURCES +=				\
> >> diff --git a/tools/Doxyfile b/tools/Doxyfile
> >> new file mode 100644
> >> index 0000000..e42cdbb
> >> --- /dev/null
> >> +++ b/tools/Doxyfile
> >> @@ -0,0 +1,318 @@
> >> +# Doxyfile 1.8.8
> >> +
> >> +#---------------------------------------------------------------------------
> >> +# Project related configuration options
> >> +#---------------------------------------------------------------------------
> >> +DOXYFILE_ENCODING      = UTF-8
> >> +PROJECT_NAME           = "Tools"
> >> +PROJECT_NUMBER         =
> > 
> > that was already pointed out elsewhere, but if we can't do the cat approach
> > from the Makefile maybe take the options that were customized and add them
> > to the end of th edoxygen file. So you know that all but the last section is
> > default gobbledegook.
> 
> I'll be switching to the cat approach. It also happens to work well on
> Windows and DevStudio, but that doesn't really matter for us.
> 
> 
> > also, what happens if we just drop all options but the customised ones? is
> > the result usable?
> 
> Not sure... but might be worth investigating.

just a follow up here: I tested this on the wayland repo and it produces the
same output. I recommend going for that approach.

[...]
> >> +
> >> +/**
> >> + at page zunitc zunitc
> >> +
> >> +- @ref zunitc_overview
> >> +- @ref zunitc_execution
> >> +  - @ref zunitc_execution_commandline
> >> +  - @ref zunitc_execution_matching
> >> +  - @ref zunitc_execution_wildcards
> >> +  - @ref zunitc_execution_repeat
> >> +  - @ref zunitc_execution_randomize
> >> +- @ref zunitc_fixtures
> >> +- @ref zunitc_functions
> > 
> > yikes, is there no way to get a page-level TOC?
> 
> Not until version 1.8.1 or later. Wayland is currently only requiring 1.6+

do we get any benefit out of not requiring 1.8.1? it was released three
years ago so I guess the real benefactor here is RHEL6. Which I obviously
support but then again this is just the documentation, not actual code that
can break.

Cheers,
   Peter


More information about the wayland-devel mailing list