Quoting Flavio Cruz (2016-04-19 01:48:50)
> This includes a set of valid and invalid definition files that MIG will
> try to process. For valid definitions, GCC will compile the stubs to
> check if valid C code was generated.
Merged, many thanks :)
Justus
On 16 April 2016 at 08:39, Samuel Thibault wrote:
> Hello,
>
> Flavio Cruz, on Wed 30 Mar 2016 02:33:37 +0200, wrote:
> > On Wed, Mar 30, 2016 at 01:41:17AM +0200, Justus Winter wrote:
> > > I like it a lot. May I suggest the following robustness fix? Seems
> > > like the empty files are lost s
Hello,
Flavio Cruz, on Wed 30 Mar 2016 02:33:37 +0200, wrote:
> On Wed, Mar 30, 2016 at 01:41:17AM +0200, Justus Winter wrote:
> > I like it a lot. May I suggest the following robustness fix? Seems
> > like the empty files are lost somewhere in my ci/package building
> > setup. Also I think we
On Wed, Mar 30, 2016 at 01:41:17AM +0200, Justus Winter wrote:
> I like it a lot. May I suggest the following robustness fix? Seems
> like the empty files are lost somewhere in my ci/package building
> setup. Also I think we want copyright notices at least in the
> framework files, not sure abou
I like it a lot. May I suggest the following robustness fix? Seems
like the empty files are lost somewhere in my ci/package building
setup. Also I think we want copyright notices at least in the
framework files, not sure about the test vectors. Thougths?
Justus
Quoting Flavio Cruz (2016-03-25 17:19:06)
> This includes a set of valid and invalid definition files that MIG will
> try to process. For valid definitions, GCC will compile the stubs to
> check if valid C code was generated.
>
> * configure.ac: Add new test Makefiles.
> * Makefile.am: Add SUBDIRS
This includes a set of valid and invalid definition files that MIG will
try to process. For valid definitions, GCC will compile the stubs to
check if valid C code was generated.
* configure.ac: Add new test Makefiles.
* Makefile.am: Add SUBDIRS.
* tests/Makeconf.am: Automake definitions shared by
Quoting Flavio Cruz (2016-03-23 01:31:13)
> This includes a set of valid and invalid definition files that MIG will
> try to process. For valid definitions, GCC will compile the stubs to
> check if valid C code was generated.
Love the idea, but 1/ this breaks out of tree (vpath) builds, 2/ I
belie
