History log of /fuchsia/zircon/system/ulib/block-client/rules.mk
Revision Date Author Comments
# b0ee6dd6 21-Sep-2018 George Kulakowski <kulakowski@google.com>

[build] Make a number of static libraries build with -fvisibility=hidden

ZX-1895 #comment
Test: CQ

Change-Id: Id3252fcb1de5a6f6e1897da86fba92e2be9d0319


# 98dec572 11-May-2018 Sean Klein <smklein@google.com>

[block-client] Add RAII C++ wrapper around block client

Test: fs, ramdisk, blobfs, fvm
ZX-2123 #done

Change-Id: I1f0d9eca48939c5c874fe5a6a9721e309e4eb338


# d53ea9b2 06-Feb-2018 P.Y. Laligand <pylaligand@google.com>

[build] Remove a few more GN files.

TO-732

Change-Id: I3d54c34deee3ddfd88705bbbfa4a9503b0bb001a


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

[zx] Magenta -> Zircon

The Great Renaming is here!

Change-Id: I3229bdeb2a3d0e40fb4db6fec8ca7d971fbffb94


# 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


# b0e8a723 13-Feb-2017 Sean Klein <smklein@google.com>

[block][ramdisk] Add FIFO support to block device

- Implemented ulib/block library to support FIFO-based block
protocol.
- Added "udev/block", acting as a global block device. Added
MX_PROTOCOL_BLOCK_CORE, which will be implemented by all
"hardware-specific" block devices. "udev/block" binds
to any hardware-specific devies that implement this protocol.
udev/block calls into the ulib/block library, which deals
with the client / server interaction.
- Updated utest/ramdisk to test the ulib/block protocol.
- Updated all uses of opening the ramdisk, so it can be accessed
through the superset of the udev/block interface.

Change-Id: I85d4d1ba70eed5c2b0bdcfbe5ff23d88afcd60cf