list & CMake 3.6.3 Documentation
List operations.
list(LENGTH &list& &output variable&)
list(GET &list& &element index& [&element index& ...]
&output variable&)
list(APPEND &list& [&element& ...])
list(FILTER &list& &INCLUDE|EXCLUDE& REGEX &regular_expression&)
list(FIND &list& &value& &output variable&)
list(INSERT &list& &element_index& &element& [&element& ...])
list(REMOVE_ITEM &list& &value& [&value& ...])
list(REMOVE_AT &list& &index& [&index& ...])
list(REMOVE_DUPLICATES &list&)
list(REVERSE &list&)
list(SORT &list&)
LENGTH will return a given list’s length.
GET will return list of elements specified by indices from the list.
APPEND will append elements to the list.
FILTER will include or remove items from the list that match the
mode’s pattern.
In REGEX mode, items will be matched against the given regular expression.
For more information on regular expressions see also the
FIND will return the index of the element specified in the list or -1
if it wasn’t found.
INSERT will insert elements to the list to the specified location.
REMOVE_AT and REMOVE_ITEM will remove items from the list.
difference is that REMOVE_ITEM will remove the given items, while
REMOVE_AT will remove the items at the given indices.
REMOVE_DUPLICATES will remove duplicated items in the list.
REVERSE reverses the contents of the list in-place.
SORT sorts the list in-place alphabetically.
The list subcommands APPEND, INSERT, FILTER, REMOVE_AT,
REMOVE_ITEM, REMOVE_DUPLICATES, REVERSE and SORT may create new
values for the list within the current CMake variable scope.
Similar to the
command, the LIST command creates new variable values in the
current scope, even if the list itself is actually defined in a parent
To propagate the results of these operations upwards, use
with PARENT_SCOPE,
CACHE INTERNAL, or some other means of value propagation.
NOTES: A list in cmake is a ; separated group of strings.
To create a
list the set command can be used.
For example, set(var a b c d e)
creates a list with a;b;c;d;e, and set(var &a b c d e&) creates a
string or a list with one item in it.
(Note macro arguments are not
variables, and therefore cannot be used in LIST commands.)
When specifying index values, if &element index& is 0 or greater, it
is indexed from the beginning of the list, with 0 representing the
first list element.
If &element index& is -1 or lesser, it is indexed
from the end of the list, with -1 representing the last list element.
Be careful when counting with negative indices: they do not start from
-0 is equivalent to 0, the first list element.cmake 3.6.3解压后可以直接用吗_百度知道
cmake 3.6.3解压后可以直接用吗
我有更好的答案
直接给你二进制程序，也可能缺少对应的库文件而不能运行也可能库文件的版本不同导致不能运行如果把库文件打包进去，就可能把你原来的冲掉，影响系统正常运行所以还是给你源码自己编译吧
采纳率：44%
来自团队：
为您推荐：
其他类似问题
换一换
回答问题，赢新手礼包
个人、企业类
违法有害信息,请在下方选择后提交
色情、暴力
我们会通过消息、邮箱等方式尽快将举报结果通知您。FindFLEX & CMake 3.6.3 Documentation
Find flex executable and provides a macro to generate custom build rules
The module defines the following variables:
FLEX_FOUND - true is flex executable is found
FLEX_EXECUTABLE - the path to the flex executable
FLEX_VERSION - the version of flex
FLEX_LIBRARIES - The flex libraries
FLEX_INCLUDE_DIRS - The path to the flex headers
The minimum required version of flex can be specified using the
standard syntax, e.g.
find_package(FLEX 2.5.13)
If flex is found on the system, the module provides the macro:
FLEX_TARGET(Name FlexInput FlexOutput
[COMPILE_FLAGS &string&]
[DEFINES_FILE &string&]
which creates a custom command to generate the &FlexOutput& file from
the &FlexInput& file.
If COMPILE_FLAGS option is specified, the next
parameter is added to the flex command line. If flex is configured to
output a header file, the DEFINES_FILE option may be used to specify its
name. Name is an alias used to get details of this custom command.
Indeed the macro defines the following variables:
FLEX_${Name}_DEFINED - true is the macro ran successfully
FLEX_${Name}_OUTPUTS - the source file generated by the custom rule, an
alias for FlexOutput
FLEX_${Name}_INPUT - the flex source file, an alias for ${FlexInput}
FLEX_${Name}_OUTPUT_HEADER - the header flex output, if any.
Flex scanners oftenly use tokens defined by Bison: the code generated
by Flex depends of the header generated by Bison.
This module also
defines a macro:
ADD_FLEX_BISON_DEPENDENCY(FlexTarget BisonTarget)
which adds the required dependency between a scanner and a parser
where &FlexTarget& and &BisonTarget& are the first parameters of
respectively FLEX_TARGET and BISON_TARGET macros.
====================================================================
find_package(BISON)
find_package(FLEX)
BISON_TARGET(MyParser parser.y ${CMAKE_CURRENT_BINARY_DIR}/parser.cpp)
FLEX_TARGET(MyScanner lexer.l
${CMAKE_CURRENT_BINARY_DIR}/lexer.cpp)
ADD_FLEX_BISON_DEPENDENCY(MyScanner MyParser)
include_directories(${CMAKE_CURRENT_BINARY_DIR})
add_executable(Foo
${BISON_MyParser_OUTPUTS}
${FLEX_MyScanner_OUTPUTS}
====================================================================他的最新文章
他的热门文章
您举报文章：
举报原因：
原文地址：
原因补充：
(最多只允许输入30个字)