Build configuration Sample Clauses

Build configuration. ‌ The build configuration file will be the CMakeLists.txt at the root of the plugin It shall look like the follows: project(TimeBenchmarking VERSION 0.1 DESCRIPTION "MY Plugin") set(CMAKE_CXX_STANDARD 14) set(PLUGIN_NAME "TimeBenchmarking") # Needed to get the function to do tests include(../../CMakeMacros/CMakeTesting.txt) # Plugins include folders include_directories(inc/) # Plugins source files list(APPEND TEST_PLUGIN_SRC src/TimeBenchmarking.cpp ) # Needed to create a shareable library add_library(${PLUGIN_NAME} SHARED ${TEST_PLUGIN_SRC}) # Target library that link against target_link_libraries(tfa) # Needed to create a version of the shared library set_target_properties(${PLUGIN_NAME} PROPERTIES SOVERSION ${PROJECT_VERSION}) Finally, it is needed to add into the parent’s folder (i.e. src_root/tfa-plugins/CMakeLists.txt) CMakeLists.txt the subdirectory of the plugin: cmake_minimum_required(VERSION 3.10) # CMake version check set(CMAKE_CXX_STANDARD 14) add_subdirectory(plugin_test) add_subdirectory(myplugin) # Add project configuration here: add_subdirectory(TimeBenchmarking) The example is available here
AutoNDA by SimpleDocs

Related to Build configuration

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Upgrade 5.1 Every version of the Software is treated as a separate product and comes under its own End-User License Agreement. By installing any other version of the Software, which is licensed under the terms of this XXXX, the Licensee terminates this Agreement according to clause 4.1.3 and enters into another End-User License Agreement that comes with the installed version.

  • Software Use Case Red Hat Enterprise Virtualization Supported on physical hardware solely to support virtual quests. Red Hat Enterprise Virtualization is designed to run and manage virtual instances and does not support user-space applications. Red Hat Enterprise Virtualization may be used as a virtual desktop infrastructure solution, however, the Subscription does not come with any software or support for the desktop operating system. You must purchase the operating system for each instance of a desktop or server separately.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Network Upgrades The Transmission Owner shall design, procure, construct, install, and own the Network Upgrades described in Attachment 6 of this Agreement. If the Transmission Owner and the Interconnection Customer agree, the Interconnection Customer may construct Network Upgrades that are located on land owned by the Interconnection Customer. Unless the Transmission Owner elects to pay for Network Upgrades, the actual cost of the Network Upgrades, including overheads, shall be borne initially by the Interconnection Customer.

Time is Money Join Law Insider Premium to draft better contracts faster.