Bruno Haible writes:
> Maybe it's more useful to randomize things? Each week, pick a different set
> of 10 modules, create a megatestdir of these modules and build & check it in
> the 20 platforms/environments that the CI supports?
That would probably work well.
Collin
Collin Funk wrote:
> It seems like a good idea to run this on less-common platforms every
> once in awhile.
>
> I thought maybe it was worth adding to CI, but it takes a long-ish time
> and I don't think headers break too frequently.
Yes, exactly: Once we've fixed the testdirs of all *-h modules,
Bruno Haible writes:
>> Wouldn't the following do the same?
>>
>> $ gnulib-tool --create-megatestdir --dir testdir1 $(gnulib-tool --list |
>> grep -- '-h$')
>
> That's what I did, yes:
> $ ./gnulib-tool --create-megatestdir --dir testdir1 --single-configure
> --with-c++-tests `cd modules
Hi Collin,
> Wouldn't the following do the same?
>
> $ gnulib-tool --create-megatestdir --dir testdir1 $(gnulib-tool --list |
> grep -- '-h$')
That's what I did, yes:
$ ./gnulib-tool --create-megatestdir --dir testdir1 --single-configure
--with-c++-tests `cd modules && echo *-h`
Bruno
Hi Bruno,
Bruno Haible via Gnulib discussion list writes:
> Building a testdir of 'selinux-h' on MSVC, I get these errors:
>
> .\selinux/selinux.h(87): error C2059: syntax error: ','
> .\selinux/selinux.h(87): error C2059: syntax error: ';'
> .\selinux/selinux.h(87): error C2061: syntax error: i
