Re: winetest: move to resources

[Alexandre Julliard]

Ferenc Wagner  writes:
> Now I got it, hopefully.  So: the winetest executable must
> contain some information about its build process which it
> can write into the reports.  These are: an identification
> string (usually the checkout date and time but possible
> something else), a URL where the executable can be
> downloaded from and a free-format block of other build info
> like toolchain versions.  Some of these are presistent, some
> more subject to change.

It sounds like what you want is a 'make dist' target that builds a
different exe for distribution, one that includes all that info. The
standard build shouldn't have to worry about these things.