Re: [IPCop-devel] Split log files by lfs files

[Gilles E. <g....@fr...>]

...
> > > I will change Config to send list of files to
> > > files_$(MACHINE)/$(STAGE_ORDER)_$(STAGE)/$(THISAPP)
> > > That name look more appropriate for the files list.
> > >
> > > Do you agree with such simple move?
> > >
> > > Another futur oriented way could be instead to create a
> > > package_$(MACHINE)/$(STAGE_ORDER)_$(STAGE) directory
> > > where to send at the same place the .log and files list.
> > > Then, on POSTBUILD, that would be easy to add package creation and
send
> > > them there.
> >
> > How about something like:
> > log_$(MACHINE)/$(STAGE_ORDER)_$(STAGE)/$(THISAPP)
> > log_$(MACHINE)/$(STAGE_ORDER)_$(STAGE)/$(THISAPP)_files
> > log_$(MACHINE)/$(STAGE_ORDER)_$(STAGE)/$(THISAPP)_missing_rootfile
>
>
> Gilles, Olaf,
>
> I like this.  Compilation log goes into $(THISAPP), installed files in
> $(THISAPP)_files and in case of a missing rootfile, we touch
> $(THISAPP)_missing_rootfile
>
> So, we won't have global log files per stage anymore?  I suggest we still
keep
> them and just cat log_$(MACHINE)/$(STAGE_ORDER)_$(STAGE)/$(THISAPP) >
> log_$(MACHINE)/_build_$(STAGE_ORDER)_$(STAGE)
>
I had my proposal done for files_$(MACHINE) but had not yet the log split
done.
I removed DIR_INFO from the TARGET line of each lfs files with a one liner
in the hope to reuse the same TARGET with a different base prefix for files.
But that does not work.
That's complicated because TARGET value need to be retrieved from make.sh.
>From Config, that value is just herited, but from make.sh, you have to
evaluate VER, PKG_NAME, THISAPP, then calculate TARGET value.

> I like to start a build and do a tail -f
> log_$(MACHINE)/_build_$(STAGE_ORDER)_$(STAGE) -- if I had to tail every
new
> log file, it would be inconvenient.
>
That's doable to have both but that will double the log size (and toolchain
log is include in toolchain package)
I would prefer only copy the latest log to log_$(MACHINE)/_latest.log

that will remain small, always the same name and at the same place.
>
> >
> > package_ instead of log_ is also OK.
>
>
> Let's keep it log_$(MACHINE).  It contains logs :-)
>
files list is not exactly a compilation log for me.

> IvanK.
>
>
What should be not hard to do for now is to
- write files list to package_$(MACHINE)/$(TARGET) wich is mostly
package_$(MACHINE)/$(STAGE_ORDER)_$(STAGE)/$(THISAPP) except for
- kernel modules where -linux is added
- binutils and gcc where -pass$(PASS) and -crosscompile is added

- write log to package_$(MACHINE)/$(STAGE_ORDER)_$(STAGE)/<lfs file
name>$(PASS)

PKG_NAME is always equal to <lfs file name>, except for
{binutils,gcc}-crosscompile
that would be even much easier if binutils and gcc pass '1' and '2' names
are changed to '-pass1' and '-pass2' or I would need to have a different
case in make.sh with PASS defined or PASS empty
No so sure yet what to do.

Gilles