Instead of using our "binaries" in our calls to pactest and vercmptest, use the
libtool linked ones. We need to ensure they are created by calling the scripts
once, and from there we can use them directly. This has some pretty large
benefits due to much reduced forking of processes.
Note: I am not sure this will work on all platforms, namely Cygwin. Further
testing is necessary.
Signed-off-by: Dan McGee <[EMAIL PROTECTED]>
---
Makefile.am | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/Makefile.am b/Makefile.am
index ea3b0e0..bc0129d 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -13,12 +13,14 @@ dist_pkgdata_DATA = PKGBUILD.proto proto.install
ChangeLog.proto
# run the pactest test suite and vercmp tests
check-local: pactest src/pacman src/util
+ $(top_builddir)/src/pacman/pacman --version || test $$? -eq 2 && true
$(PYTHON) $(top_srcdir)/pactest/pactest.py --debug=1 \
--test $(top_srcdir)/pactest/tests/*.py \
- -p $(top_builddir)/src/pacman/pacman
+ -p $(top_builddir)/src/pacman/.libs/lt-pacman
rm -rf $(top_builddir)/root
+ $(top_builddir)/src/util/vercmp || test $$? -eq 2 && true
$(SH) $(top_srcdir)/pactest/vercmptest.sh \
- $(top_builddir)/src/util/vercmp
+ $(top_builddir)/src/util/.libs/lt-vercmp
# create the pacman DB and cache directories upon install
install-data-local:
--
1.5.6.3
_______________________________________________
pacman-dev mailing list
[email protected]
http://archlinux.org/mailman/listinfo/pacman-dev
