public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: John Stultz <jstultz@google.com>, ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH 2/2] sched_football: Rewrite into new API
Date: Mon, 15 Jul 2024 14:44:23 +0200	[thread overview]
Message-ID: <20240715124423.GC424468@pevik> (raw)
In-Reply-To: <ZpT8QdtUZydGj6lN@yuki>

> Hi!
> > > And the main problem with our build system is not the tooling we choose,
> > > but the complexity imposed by the out-of-tree build implemented in the
> > > complex makefiles. As far as I can tell 99% of the problems would be
> > > solved by ripping out out-of-tree support, which would remove most of
> > > the code we have in there.

> > +1 for removal. I wonder if anybody finds a time to do that.

> That is unfortunatelly a major task...

> > > > But back to the reality, would it be possible to merge this even with broken
> > > > dependency? I'm not sure myself.

> > > I will double check the code, before adding my final reviewed-by.

> > Thank you! It still bothers me that building sched_football does not trigger
> > building a library, but at least it will work for a full build (building whole
> > LTP).

> It's even more subtle, there are more things to consider. The test
> should be rebuild even if any of the headers it includes change, which
> is not detected properly at the moment. For that to work first thing the
> build system has to do is to generate a dependencies with $(CC) -MM and
> then include them in the build system.

Cool, it really detects required headers.
$ gcc -MM  -I../../include tst_needs_cmds04.c
tst_needs_cmds04.o: tst_needs_cmds04.c ../../include/tst_test.h \
 ../../include/tst_common.h ../../include/tst_res_flags.h \
 ../../include/tst_parse.h ../../include/tst_test_macros.h \
 ../../include/tst_checkpoint.h ../../include/tst_checkpoint_fn.h \
 ../../include/tst_device.h ../../include/tst_mkfs.h \
 ../../include/tst_fs.h ../../include/tst_pid.h ../../include/tst_cmd.h \
 ../../include/tst_cpu.h ../../include/tst_process_state.h \
...
 ../../include/tst_cgroup.h

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-07-15 12:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 10:43 [LTP] [RFC PATCH 1/2] realtime: Use offsetof() macro from <stddef.h> Petr Vorel
2024-07-11 10:43 ` [LTP] [RFC PATCH 2/2] sched_football: Rewrite into new API Petr Vorel
2024-07-12 11:21   ` Cyril Hrubis
2024-07-12 13:22     ` Petr Vorel
2024-07-12 14:11       ` Cyril Hrubis
2024-07-12 19:09         ` Petr Vorel
2024-07-15  9:07           ` Cyril Hrubis
2024-07-15  9:52             ` Petr Vorel
2024-07-15 10:38               ` Cyril Hrubis
2024-07-15 12:44                 ` Petr Vorel [this message]
2024-07-17 14:52   ` Cyril Hrubis
2024-07-17 16:03     ` Petr Vorel
2024-07-12  9:57 ` [LTP] [RFC PATCH 1/2] realtime: Use offsetof() macro from <stddef.h> Cyril Hrubis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240715124423.GC424468@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@suse.cz \
    --cc=jstultz@google.com \
    --cc=ltp@lists.linux.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox