Ben Walker 9dd998cdc0 Add a configure script to generate the CONFIG file ... Add a configure script in the root of the repository that looks and feels like one that would be generated by autotools. This script simply generates a CONFIG file for you, which used to be done by hand. Now to build SPDK you can do the following: ./configure --with-dpdk=path make Change-Id: I44ebb91f0cb1468b86da4c0033ac1406595d4967 Signed-off-by: Ben Walker <benjamin.walker@intel.com>		2017-04-03 13:30:12 -07:00
..
ioat.unittest.mk	build: define SPDK_LIB_LIST to simplify building dependencies and linker args	2016-11-22 11:45:48 -07:00
json.unittest.mk	json: add printf-style spdk_json_write_string_fmt()	2016-11-22 16:32:35 -07:00
nvme.libtest.mk	build: define SPDK_LIB_LIST to simplify building dependencies and linker args	2016-11-22 11:45:48 -07:00
nvme.unittest.mk	test/nvme: don't link unit tests against spdk_nvme	2016-12-08 14:19:25 -07:00
nvmf.unittest.mk	nvmf: split discovery service into its own file	2017-03-17 15:55:36 -07:00
spdk.app.mk	vhost: add a library and app for userspace vhost-scsi processing	2017-03-06 12:44:35 -07:00
spdk.common.mk	Add a configure script to generate the CONFIG file	2017-04-03 13:30:12 -07:00
spdk.deps.mk	build: add copyright header where missing	2016-11-22 16:41:47 -07:00
spdk.lib.mk	build: define SPDK_LIB_LIST to simplify building dependencies and linker args	2016-11-22 11:45:48 -07:00
spdk.modules.mk	bdev: add "split" virtual blockdev example	2017-01-30 13:51:18 -07:00
spdk.subdirs.mk	build: add copyright header where missing	2016-11-22 16:41:47 -07:00