aboutsummaryrefslogtreecommitdiff
path: root/run_cross_test.py
AgeCommit message (Collapse)AuthorFilesLines
2020-10-13cmake: Add cross testsDaniel Mensinger1-4/+16
2020-09-11Add build machine compilers to project tests compiler reportJon Turney1-1/+0
When cross-compiling, also report build machine compilers in the compiler report produced by run_project_tests.py
2020-09-11Add a test run of MSVC ARM64 cross on Windows x64Jon Turney1-1/+8
Add a cross-file for MSVC UWP ARM64. Bump cidata tag to get an updated install.ps1 script (run by run.ps1) which sets the vcvars environment correctly when cross-compiling. Since arranging the correct environment for simultaneous cross and native 'cl' use is hard, this is test run uses '--cross-only' so we don't require a native compiler. Extend '--cross-only' so it also explicitly uses a machine file which makes all build machine compilers unusable.
2020-09-10Add a test run in an environment which only has a cross compilerJon Turney1-3/+6
Add '--cross-only' option to run_tests.py, so we can arrange not to run tests in the 'native' suite when only a cross-compiler is available, as they can't succeed.
2020-09-10Split tests out from 'common' which require a native compilerJon Turney1-1/+1
Split out tests (and parts of tests) which require a native compiler from the 'common' suite to a new suite called 'native', so we can selectively avoid running those tests when only a cross-compiler is available. Also move test '211 cmake module' to 'cmake' suite, since it appears that the way we use cmake requires a native compiler.
2020-06-15run_*tests*.py: print Meson version at start of test suiteMichael Hirsch1-2/+4
on some systems, tests may take over an hour to run--only to find you might have used an unintended Meson version (e.g. release instead of dev). This change prints the Meson version at the start of the run_*tests*.py scripts. Also, raise SystemExit(main()) is preferred in general over sys.exit(main())
2020-01-28Make run_cross_test.py just a wrapper around run_project_tests.pyJon Turney1-26/+8
This makes the platform_fix_name() machinery for toolchains which don't have gcc-like filename conventions available to cross testing.
2019-04-05run_cross_tests: Pass correct argumentDylan Baker1-1/+1
I don't konw how the heck this has ever worked, but you know.
2018-10-14Merge pull request #4340 from jon-turney/azure-pipelinesJussi Pakkanen1-1/+1
Add Azure pipelines CI
2018-10-14Use 'CI' environment variable to detect CI environmentJon Turney1-1/+1
Use the 'CI' environment variable to detect CI environment, rather than a collection of CI-specific ones.
2018-10-10Add option to fail fast in testsNiklas Claesson1-3/+5
2018-10-10tests runners: Refactor out global variables and add argparseNiklas Claesson1-6/+12
2018-05-31Revert "mesonlib: handle meson exe wrappers"Nirbheek Chauhan1-2/+0
This reverts commit 0627e9d616dc311b7c9b0ef17301f680ac9e78a7. Breaks installation: https://github.com/mesonbuild/meson/issues/3647 Will be restored once that can be fixed.
2018-05-30mesonlib: handle meson exe wrappersMartin Kelly1-0/+2
There are cases when it is useful to wrap the main meson executable with a script that sets up environment variables, passes --cross-file, etc. For example, in a Yocto SDK, we need to point to the right meson.cross so that everything "just works", and we need to alter CC, CXX, etc. In such cases, it can happen that the "meson" found in the path is actually a wrapper script that invokes the real meson, which may be in another location (e.g. "meson.real" or similar). Currently, in such a situation, meson gets confused because it tries to invoke itself using the "meson" executable (which points to the wrapper script) instead of the actual meson (which may be called "meson.real" or similar). In fact, the wrapper script is not necessarily even Python, so the whole thing fails. Fix this by using Python imports to directly find mesonmain.py instead of trying to detect it heuristically. In addition to fixing the wrapper issue, this should make the detection logic much more robust.
2018-04-26Prettifying some output with pathlibNiklas Claesson1-2/+4
2016-12-20Make cross tests use same framework as regular tests.Jussi Pakkanen1-59/+18
2016-12-20Fix cross test and run them if a cross compiler is available.Jussi Pakkanen1-1/+1
2016-07-19Normalize the path of a configured file to avoid dupes (#640)Nirbheek Chauhan1-1/+1
2016-01-16Renamed meson package to mesonbuild so that we can have a script named meson ↵Jussi Pakkanen1-1/+1
in the same toplevel dir.
2016-01-16Finalize moduleification so that full test suite runs.Jussi Pakkanen1-2/+2
2015-05-09Fix cross compilation tests.Jussi Pakkanen1-2/+4
2015-02-16Use lib as library path in unit tests.Jussi Pakkanen1-1/+1
2014-11-16Harmonised copyright declarations.Jussi Pakkanen1-1/+1
2014-08-11Updated copyright years.Jussi Pakkanen1-1/+1
2013-09-30Can specify cross file as a command line argument.Jussi Pakkanen1-2/+1
2013-08-30Better build type introspection.Jussi Pakkanen1-2/+2
2013-08-30The whole test suite runs cross-built with mingw and armhf.Jussi Pakkanen1-1/+2
2013-08-30Work started on supporting simultaneous native and cross builds.Jussi Pakkanen1-1/+0
2013-08-24Get has_function from cross file.Jussi Pakkanen1-1/+1
2013-08-24Get sizeof info from cross file if it exists and write an error if it can ↵Jussi Pakkanen1-0/+1
not be determined.
2013-08-24Skip tests for cross compilation when they can not be run.Jussi Pakkanen1-2/+1
2013-08-24Updated symbolextractor to work with cross builds.Jussi Pakkanen1-0/+88