[Toybox] [PATCH] new Android toy: log

[enh]

On Sat, Jun 25, 2016 at 11:53 PM, Rob Landley <rob at landley.net> wrote:
> On 06/25/2016 04:17 PM, enh wrote:
>> On Sat, Jun 25, 2016 at 10:34 AM, Rob Landley <rob at landley.net> wrote:
>> (even if we had the #ifdefs, being able to point to an arbitrary
>> directory for the generated files would be independently useful to me
>> because it would let me stop checking in generated files.)
>
> Hmmm, I'd assumed you'd just drop a symlink if you needed a different
> location.

the point isn't that we need a _different_ location --- it's that we
need two locations because without my #ifdef hacks we can't build the
same .config for both host and target. so we need two .config files in
the same build tree, and two generated/ directories.

> I can make it configurable, but it's a bit tricky (have to set
> the default in more than one place because configure is shell syntax and
> Makefile is makefile syntax, and yes this is already an issue for CC.)
>
>> but like i said, no one's working on either of these things right now,
>> so it probably doesn't make sense for you to look at doing anything
>> until i can promise i'd actually investigate using it in a reasonable
>> timeframe. maybe next year...
>
> I prefer to have things ready for when you have time. Ordinarily your
> time is more of a limiting factor. (Not the past few weeks, but that's
> startup funding crises for you...)
>
>>>> this isn't something that anyone's currently actively working on
>>>> though. we have other major build system upheavals to get through
>>>> first :-)
>>>
>>> I'm working on it, but I $DAYJOB isn't giving me a lot of air at the
>>> moment. (I'm either riding down a fourth startup or I'll get
>>> retroactively paid for the past 6 weeks. No idea which yet.)
>>>
>>>> (bionic is soong-only at this point in master. [most of] the makefiles
>>>> have been deleted.)
>>>
>>> You can delete toybox's makefile for the actual build and just run the
>>> shell scripts directly (at least to get a host version), and all we use
>>> from kconfig is the .config file. (And I could probably make a sed
>>> invocation generate a defconfig, or repurpose the scripts/config2help.c
>>> plumbing. I've been meaning to write a full kconfig replacement for
>>> years, it just hasn't made it up the todo list...)
>>
>> the kconfig stuff stopped working for me a while back (long enough
>> that i forget why) --- i've just edited .config directly for a very
>> long time now. (i think there was a thread on the list about using the
>> awk version instead around that time.)
>
> Right, I need to bump kconfig replacement up near the top of my todo list.

not on my account --- honestly, editing the .config file directly is
less effort than dealing with that awful 1980s DOS app imitation ever
was.

> I need like a month's vacation in an otherwise empty hotel room to catch
> up on _just_ my toybox todo list. (In the meantime, back to the
> "potential customer needs an SDK by monday" crisis du jour...)
>
>>> Rob
>
> Rob



-- 
Elliott Hughes - http://who/enh - http://jessies.org/~enh/
Android native code/tools questions? Mail me/drop by/add me as a reviewer.