S. Gilles and you have pointed same negative property of sh -
readability. I agree that plane mk is good enough for static or almost
static configurations. Say I need to pass some -D flags according to
configuration/environment and such defines are meaningful and needed
only in current sub-module.
On Wed, Jul 26, 2017 at 09:32:15AM -0700, Michael Forney wrote:
> … Anyway, I'm a little suprised about the distaste for ninja since
> it's features are pretty much the same as POSIX make (variable
> assignments and rule definitions).
I suppose the last half of that sentence outlines the distaste
On 26 July 2017 at 18:32, Michael Forney wrote:
> On 7/26/17, Anselm R Garbe wrote:
>> Out of curiosity, what is the point of a build system like ninja, if
>> the codebase requires to be complex?
>
[..]
> In oasis I'm using ninja like you're use stali.mk in stali. The
> advantage is that dependen
On Wed, Jul 26, 2017 at 12:05:01PM -0500, Joshua Haase wrote:
> Anselm R Garbe writes:
>
> > IMHO this view is short sighted. The point of an _issue_ tracker (not
> > every issue is a bug) is not the possibility to flood the developer
> > with random bug reports, but to provide a simple infrastru
Anselm R Garbe writes:
> IMHO this view is short sighted. The point of an _issue_ tracker (not
> every issue is a bug) is not the possibility to flood the developer
> with random bug reports, but to provide a simple infrastructure to
> organize and priotize a TODO list for the development of a ce
On 7/26/17, Anselm R Garbe wrote:
> On 26 July 2017 at 09:05, Silvan Jegen wrote:
>> That's what I suspected. Not sure it's desirable to ever work on a
>> codebase big enough to require a build system which uses ninja under
>> the hood. If I find myself in such a position I will turn to samurai
>
Hi,
Since I'm currently rebuilding a desktop gnu/linux distro from _my_ scratch:
- the wayland stack did switch to meson(python3)/ninja(c++). meson is
handling "classic" cases, but if you go in corner cases, it breaks
easily, for instance, if you want static libs/bins
On 26 July 2017 at 03:28, ochern wrote:
> That's right. No new build system is suggested.
>
> Let me suggest a small poll:
> 1 What build systems do you consider as most suckless?
Plain mkfiles + rc or plain Makefile's + sh and sbase-compliant command usage.
> 2 Generating Makefile from a shell
On Wed, Jul 26, 2017 at 9:25 AM, Anselm R Garbe wrote:
> On 26 July 2017 at 09:05, Silvan Jegen wrote:
>> On Wed, Jul 26, 2017 at 8:57 AM, Michael Forney wrote:
>>> On 7/25/17, Silvan Jegen wrote:
On Wed, Jul 26, 2017 at 7:32 AM, Michael Forney
> Even if you don't care for ninja, it d
On 25 July 2017 at 11:59, Laslo Hunhold wrote:
> On Mon, 24 Jul 2017 22:13:36 -0500
> Joshua Haase wrote:
>> I do think a good issue tracker is needed and would be willing to
>> contribute on september 2-3 (although maybe in a different time zone:
>> [UTC-6]).
>>
>> As for useless bug reports, a
On 26 July 2017 at 09:05, Silvan Jegen wrote:
> On Wed, Jul 26, 2017 at 8:57 AM, Michael Forney wrote:
>> On 7/25/17, Silvan Jegen wrote:
>>> On Wed, Jul 26, 2017 at 7:32 AM, Michael Forney
Even if you don't care for ninja, it does seem to be gaining
popularity, and I've noticed sever
On Wed, Jul 26, 2017 at 8:57 AM, Michael Forney wrote:
> On 7/25/17, Silvan Jegen wrote:
>> On Wed, Jul 26, 2017 at 7:32 AM, Michael Forney
>>> Even if you don't care for ninja, it does seem to be gaining
>>> popularity, and I've noticed several projects start switching from
>>> autotools to mes
12 matches
Mail list logo
