All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 2/2] Add Linux Test eXecutor inside tools
Date: Mon, 18 Sep 2023 11:42:07 +0200	[thread overview]
Message-ID: <ZQgbbx2MEsJaKWwR@yuki> (raw)
In-Reply-To: <ZQgarkBUEyDd4lxF@yuki>

Hi!
> Unfortunately this does not work well either because the ltx does not
> have install targed and trying to install a file from a subdirectory is
> not possible with the LTP build system. I've tried that and it didn't
> work.
> 
> Let's merge this version that works, we can try to do make things better
> later on.

Also one more point $(MAKE) -C ltx-src does not support out-of-tree
build and while it's probably fine for 'make check' not to support it,
since that is a developer tooling, it should work fine for ltx that is
going to be packaged/installed on the SUT.

So I suppose that we are stuck with the LTP ltx Makefile unless we:

- add support for out-of-tree build to ltx/Makefile
- drop out-of-tree build support from LTP

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2023-09-18  9:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18  8:25 [LTP] [PATCH v3 0/2] Add kirk & ltx tools Andrea Cervesato
2023-09-18  8:25 ` [LTP] [PATCH v3 1/2] Replace runltp-ng with kirk framework Andrea Cervesato
2023-09-18  9:01   ` Petr Vorel
2023-09-18  9:06     ` Andrea Cervesato via ltp
2023-09-18  8:25 ` [LTP] [PATCH v3 2/2] Add Linux Test eXecutor inside tools Andrea Cervesato
2023-09-18  9:17   ` Petr Vorel
2023-09-18  9:35     ` Andrea Cervesato via ltp
2023-09-18  9:38     ` Cyril Hrubis
2023-09-18  9:42       ` Cyril Hrubis [this message]
2023-09-18 10:34         ` Petr Vorel
2023-09-18 10:37       ` Petr Vorel

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=ZQgbbx2MEsJaKWwR@yuki \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.