bareflank-hypervisor/scripts/cmake/config/example_extension.cmake
Rian Quinn aab477a590
Build System Bug Fixes (#575)
This patch addresses several bugs with the build system:
- Lack of Windows support
- Clang Tidy was not working properly
- Making modifications to the source code would compile, but would not
re-link resulting in issues
- Removed excess file copying
- Make clean now works
- Removed unused or confusing folders in the build folder as part of the
build process. It is now much easier to traverse the build folder for
dependencies
- The targets didn't work with extensions. This has been fixed.

In addition, the following was also done under this patch
- Intrinsics was moved to the top level and out of the VMM
- Platform files are now in a folder called "platform" instead of
"arch"
- All subprojects have the same include/src/tests files structure
- All intel specific code is properly organized to match intended
namespacing
- Removed dead code
- A small part of the VMCS was converted to use the delegate pattern
- All dependencies are now downloaded at configure time instead of
compile time.
- The cache directory is now cached by Travis CI
- CMake output better matches old build system
- Added make rebuild and separate clean targets to remove various parts
of the build depending on needs.
- Added targets for Clean, Tidy, Rebuild and Format for each subproject
- Re-organized the cmake logic so that macros are not spread out
- New validation removes unneeded complexity
- Removed the need for the compiler wrapper, and in doing so, we now
provide a simpilar set of toolchain files
- Removed the need for Git repos. All external dependencies are
downloaded using a zip or tarball
- Libcxx and Libcxxabi are now in their own files. Much similar logic
- Unit test CMake files have been greatly simplified
- Each subproject is unaware of it's prefix and no long use VMM,
USERSPACE or TEST variables in their cmake files
- Fixed bugs with the flags
- Renamed the varbiables in the default.cmake config to be more
consistent and easier to follow in the rest of the code

Signed-off-by: “rianquinn” <“rianquinn@gmail.com”>
2018-01-22 12:45:07 -07:00

61 lines
2.2 KiB
CMake

#
# Bareflank Hypervisor
# Copyright (C) 2015 Assured Information Security, Inc.
#
# This library is free software; you can redistribute it and/or
# modify it under the terms of the GNU Lesser General Public
# License as published by the Free Software Foundation; either
# version 2.1 of the License, or (at your option) any later version.
#
# This library is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# Lesser General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public
# License along with this library; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
# ------------------------------------------------------------------------------
# README
# ------------------------------------------------------------------------------
# For a complete example of how to use a VMM extension, please see the
# following example:
# https://github.com/Bareflank/hypervisor_example_cpuidcount
# ------------------------------------------------------------------------------
# Extension
# ------------------------------------------------------------------------------
# Add Subproject
#
# To add an extension, use the add_subproject macro. This macro tells the build
# system to include an external project. This is the same macro used by the
# main build system. Like the main build system, the extension must contain
# it's own sub project.
#
#add_subproject(
# <name> vmm
# DEPENDS bfvmm bfintrinsics <dependencies>
# SOURCE_DIR <path>
#)
# Subproject Layout
#
# Like all subprojects, your project must start with cmake's project macro.
# In addition, the init_project macro must be used which ensures the projects
# variables are properly setup based on the prefix you intend to use (which
# will likely be the "vmm"). Finally, you can use the add_xxx_library
# functions or you can use the add_vmm_executable function as shown in
# this example.
#
#cmake_minimum_required(VERSION 3.6)
#project(example_vmm C CXX)
#
#include(${SOURCE_CMAKE_DIR}/project.cmake)
#init_project()
#
#add_vmm_executable(example_vmm
# SOURCES <filename>.cpp
#)