From: Saul Wold <sgw@linux.intel.com>
To: linux-modules@vger.kernel.org
Subject: [PATCH] Makefile.am: add mkdir testsuite and standaline build target
Date: Wed, 9 Oct 2013 15:53:47 -0700 [thread overview]
Message-ID: <1381359227-29867-1-git-send-email-sgw@linux.intel.com> (raw)
If we are not building in the existing source tree, the testsuite
directory will not exist so the cp of the stamp-rootfs would fail.
Also added buildtest-TESTS so they could be build in the cross env,
without running the tests.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
Makefile.am | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Makefile.am b/Makefile.am
index c165868..018e6ed 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -131,7 +131,7 @@ endif
ROOTFS = testsuite/rootfs
ROOTFS_PRISTINE = $(top_srcdir)/testsuite/rootfs-pristine
-CREATE_ROOTFS = $(AM_V_GEN) ( $(RM) -rf $(ROOTFS) && \
+CREATE_ROOTFS = $(AM_V_GEN) ( $(RM) -rf $(ROOTFS) && mkdir -p $(dir $(ROOTFS)) && \
cp -r $(ROOTFS_PRISTINE) $(ROOTFS) && \
touch testsuite/stamp-rootfs && \
find $(ROOTFS) -type d -exec chmod +w {} \; )
@@ -217,6 +217,9 @@ DISTCHECK_CONFIGURE_FLAGS=--enable-gtk-doc --sysconfdir=/etc --with-zlib
distclean-local: $(DISTCLEAN_LOCAL_HOOKS)
+buildtest-TESTS:
+ $(MAKE) $(AM_MAKEFLAGS) $(check_LTLIBRARIES) $(check_PROGRAMS)
+
# ------------------------------------------------------------------------------
# custom release helpers
# ------------------------------------------------------------------------------
--
1.8.3.1
next reply other threads:[~2013-10-09 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 22:53 Saul Wold [this message]
2013-10-09 23:30 ` [PATCH] Makefile.am: add mkdir testsuite and standaline build target Lucas De Marchi
2013-10-10 0:39 ` Saul Wold
2013-10-10 0:55 ` Lucas De Marchi
2013-10-10 1:14 ` Saul Wold
2013-10-10 4:15 ` Lucas De Marchi
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=1381359227-29867-1-git-send-email-sgw@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=linux-modules@vger.kernel.org \
/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.