On Thu, Nov 01, 2018 at 06:38:03PM -0700, Andrew Gregory wrote:
> On 11/01/18 at 08:51pm, Dave Reisner wrote:
> > On Thu, Nov 01, 2018 at 01:03:27AM -0700, Andrew Gregory wrote:
> > > On 10/21/18 at 05:46pm, Dave Reisner wrote:
>
> ...
>
> > > > +libcommon = static_library(
> > > > + 'common',
>
On 11/01/18 at 08:51pm, Dave Reisner wrote:
> On Thu, Nov 01, 2018 at 01:03:27AM -0700, Andrew Gregory wrote:
> > On 10/21/18 at 05:46pm, Dave Reisner wrote:
...
> > > +libcommon = static_library(
> > > + 'common',
> > > + libcommon_sources,
> > > + install : false)
> >
> > It's a mistake, bu
On Thu, Nov 01, 2018 at 01:03:27AM -0700, Andrew Gregory wrote:
> On 10/21/18 at 05:46pm, Dave Reisner wrote:
>
> -- >8 -- (lots of words)
>
> > diff --git a/meson.build b/meson.build
> > new file mode 100644
> > index ..3f9b2ae0
> > --- /dev/null
> > +++ b/meson.build
> > @@ -0,0 +1,487
On 10/21/18 at 05:46pm, Dave Reisner wrote:
-- >8 -- (lots of words)
> diff --git a/meson.build b/meson.build
> new file mode 100644
> index ..3f9b2ae0
> --- /dev/null
> +++ b/meson.build
> @@ -0,0 +1,487 @@
-- >8 -- (many more words)
> +PYTHON = find_program('python')
This should look
On Sun, Oct 21, 2018 at 10:11:18PM -0400, Dave Reisner wrote:
> On Mon, Oct 22, 2018 at 11:16:25AM +1000, Allan McRae wrote:
> > On 22/10/18 10:03 am, Dave Reisner wrote:
> > > On Mon, Oct 22, 2018 at 09:56:04AM +1000, Allan McRae wrote:
> > >> On 22/10/18 8:57 am, Eli Schwartz wrote:
> > Also
On Mon, Oct 22, 2018 at 11:16:25AM +1000, Allan McRae wrote:
> On 22/10/18 10:03 am, Dave Reisner wrote:
> > On Mon, Oct 22, 2018 at 09:56:04AM +1000, Allan McRae wrote:
> >> On 22/10/18 8:57 am, Eli Schwartz wrote:
> Also, most projects ship prebuilt man pages. I think some GNU ones
> co
On 10/21/18 9:32 PM, Eli Schwartz wrote:
> On 10/21/18 9:16 PM, Allan McRae wrote:
>> None need solved for inclusion in the current state. I'm just trying to
>> understand what our future release process will look like.
>>
>> While we have autotools in parallel, if I run "make dist" with this
>> p
On 10/21/18 9:16 PM, Allan McRae wrote:
> On 22/10/18 10:03 am, Dave Reisner wrote:
>> On Mon, Oct 22, 2018 at 09:56:04AM +1000, Allan McRae wrote:
>>> On 22/10/18 8:57 am, Eli Schwartz wrote:
> Also, most projects ship prebuilt man pages. I think some GNU ones
> commit the built page to th
On 22/10/18 10:03 am, Dave Reisner wrote:
> On Mon, Oct 22, 2018 at 09:56:04AM +1000, Allan McRae wrote:
>> On 22/10/18 8:57 am, Eli Schwartz wrote:
Also, most projects ship prebuilt man pages. I think some GNU ones
commit the built page to the tree, so that could be an option.
>>
>>> Bot
On 10/21/18 7:56 PM, Allan McRae wrote:
> On 22/10/18 8:57 am, Eli Schwartz wrote:
>>> Also, most projects ship prebuilt man pages. I think some GNU ones
>>> commit the built page to the tree, so that could be an option.
>
>> Both those things are also true about the configure and Makefile.in file
On Mon, Oct 22, 2018 at 09:56:04AM +1000, Allan McRae wrote:
> On 22/10/18 8:57 am, Eli Schwartz wrote:
> >> Also, most projects ship prebuilt man pages. I think some GNU ones
> >> commit the built page to the tree, so that could be an option.
>
> > Both those things are also true about the config
On 22/10/18 8:57 am, Eli Schwartz wrote:
>> Also, most projects ship prebuilt man pages. I think some GNU ones
>> commit the built page to the tree, so that could be an option.
> Both those things are also true about the configure and Makefile.in files...
That is another good reason not to use gi
On 10/21/18 6:26 PM, Allan McRae wrote:
> On 22/10/18 8:12 am, Dave Reisner wrote:
>> On Mon, Oct 22, 2018 at 07:54:57AM +1000, Allan McRae wrote:
>>> On 22/10/18 7:46 am, Dave Reisner wrote:
3) No 'make dist' equivalent. Just run 'git archive' to generate a
suitable tarball for distribut
On 22/10/18 8:12 am, Dave Reisner wrote:
> On Mon, Oct 22, 2018 at 07:54:57AM +1000, Allan McRae wrote:
>> On 22/10/18 7:46 am, Dave Reisner wrote:
>>> 3) No 'make dist' equivalent. Just run 'git archive' to generate a
>>> suitable tarball for distribution.
>>
>> Is there a way to include pregenera
On 10/21/18 6:12 PM, Dave Reisner wrote:
> On Mon, Oct 22, 2018 at 07:54:57AM +1000, Allan McRae wrote:
>> On 22/10/18 7:46 am, Dave Reisner wrote:
>>> 3) No 'make dist' equivalent. Just run 'git archive' to generate a
>>> suitable tarball for distribution.
>>
>> Is there a way to include pregenera
On Mon, Oct 22, 2018 at 07:54:57AM +1000, Allan McRae wrote:
> On 22/10/18 7:46 am, Dave Reisner wrote:
> > 3) No 'make dist' equivalent. Just run 'git archive' to generate a
> > suitable tarball for distribution.
>
> Is there a way to include pregenerated man pages with git archive?
>
> A
No, g
On 22/10/18 7:46 am, Dave Reisner wrote:
> 3) No 'make dist' equivalent. Just run 'git archive' to generate a
> suitable tarball for distribution.
Is there a way to include pregenerated man pages with git archive?
A
Provide both build systems in parallel for now, to ensure that we work
out all the differences between the two. Some time from now, we'll give
up on autotools.
Meson tends to be faster and probably easier to read/maintain. On my
machine, the full meson configure+build+install takes a little under
18 matches
Mail list logo
