History log of /fuchsia/zircon/system/utest/core/stack/rules.mk
Revision Date Author Comments
# fa572f73 27-Feb-2018 Roland McGrath <mcgrathr@google.com>

[utest][core][stack] Don't use -fsanitize=safe-stack under ASan

These options are incompatible.

Change-Id: I4ee0c5d3b1ea5cd17fe718ad753cf4af588a5fde


# f3e2126c 12-Sep-2017 Roland McGrath <mcgrathr@google.com>

[zx] Magenta -> Zircon

The Great Renaming is here!

Change-Id: I3229bdeb2a3d0e40fb4db6fec8ca7d971fbffb94


# 70435694 19-Apr-2017 Yvonne Yip <yky@google.com>

[utest] run magenta tests in groups

Assign a group to magenta tests, and run tests in order of
increasing complexity, and abort the test if a group failed.
This is because if there is a bug in a core magenta facility,
it could cause all higher level tests to fail.

The current groups are:

* "core": tests on kernel facilities
* "ddk": ddk tests
* "sys": general magenta system tests (default)
* "fs": filesystem tests

Set the group in the tests' rules.mk by setting the
MODULE_USERTEST_GROUP variable.

runtests accepts a list of groups to run. If none is specified,
run all tests.

Change-Id: Ia363d25f5c1c828a3d1a9abf586170bb90c679f7


# 16656ae0 05-Apr-2017 Brian Swetland <swetland@google.com>

[build] flatten the build

Previously we treated kernel/, system/, and third_party/ as
overlays on a shared namespace. This required the concept
of "canonical" module names, and a lot of complexity to ensure
that things didn't collide and the build worked.

This change gets rid of that, no longer passes -I to make,
so that include directives from our *.mk files do not magically
wildcard across various paths, etc.

The most user-visible change is that everywhere where a module
name is specified (MODULE_DEPS, MODULE_LIBS, etc), full module
names like kernel/lib/io or system/ulib/mxio must be used instead
of previously-allowed "short" names like lib/io and ulib/mxio.

The build output still has a similar shape, but the first segment
of the module path (kernel/, system/, or third_party/) is no
longer elided under $(BUILDDIR)

Change-Id: I525aba1da1c86eb7a86007bddc669f7eeebfedd5


# 12242caa 07-Mar-2017 Brian Swetland <swetland@google.com>

[build][musl] refer to musl libc as ulib/c

This makes the build rules and the intermediate
output files easier to understand, without having
to modify the path where musl libc lives.

The biggest observeable difference is the build
intermediate files:

$ ls build-magenta-pc-x86-64/ulib/c
config-module.h libc.abi.h libc.abi.stamp libc.so libc.so.id libc.so.strip
libc.a libc.abi.o libc.a.opts libc.so.abi libc.so.opts third_party

which previously were at build-magenta-pc-x86/ulib/musl
and named libmusl.*

and the replacing of ulib/musl with ulib/c in the library
dependencies of all the rules.mk files (the vast bulk of
this change)

Change-Id: If9c5d522099d2c9ac5bdb666b8e67a2eb3d316ee


# 248fded3 20-Feb-2017 Roland McGrath <mcgrathr@google.com>

[utest][core] Add test of stack invariants

Change-Id: I6d45bed4a0a5ec194d13e1564e928a3a7f019ebf