Re: Package custom build steps

One more thing -- it would be nice if these commands had access to the various build directories (under bin/target/.../pkgname/... or similar): - temp directory to dump non-buildables - generated src directory that's included in both the src and the include path during the build - output

Re: Package custom build steps

Hi Simon, On Sun, Feb 26, 2017 at 01:31:39PM -0800, Simon Ratner wrote: > Hi devs, > > I have a package that requires a custom build step (generating intermediate > files). Any recommendations on how to best handle this? > > Currently I am doing the custom step from my top-level makefile,

Re: newt size improvements

Also, any chance output could be limited to 80 columns? On Sun, Feb 26, 2017 at 2:53 PM, Simon Ratner wrote: > Looks neat, but when I run it, I don't get the tree -- everything is > lumped under "(other)". Any ideas? > > On Sun, Feb 26, 2017 at 2:09 PM, Vipul Rahane

Re: newt size improvements

+1. Looks quite useful. > On Feb 26, 2017, at 7:51 AM, Jim Jagielski wrote: > > +1 >> On Feb 23, 2017, at 1:16 PM, Sterling Hughes >> wrote: >> >> Neat :) You parse an elf and write sections to a sqlite db, and then allow >> queries

Package custom build steps

Hi devs, I have a package that requires a custom build step (generating intermediate files). Any recommendations on how to best handle this? Currently I am doing the custom step from my top-level makefile, before invoking `newt build`, but that doesn't seem ideal. Cheers, simon

Re: newt size improvements

+1 > On Feb 23, 2017, at 1:16 PM, Sterling Hughes > wrote: > > Neat :) You parse an elf and write sections to a sqlite db, and then allow > queries against that. > > Sterling > > On 23 Feb 2017, at 10:13, Kevin Townsend wrote: > >> This looks really