blocks|key|1708534|text|对于make：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1708535|sourcecode.h+sourcecode.cpp:+sourcecode.lzz
<TAB>lazy-cpp+sourcecode.lzz|code-block|syntax|javascript|1708536|用正确的值填充sourecode.h、sourcecode.cpp和lazy-cpp。我不认识他们。|1708537|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

For make:

<pre><code>sourcecode.h sourcecode.cpp: sourcecode.lzz
&lt;TAB&gt;lazy-cpp sourcecode.lzz
</code></pre>

fill in sourcecode.h, sourcecode.cpp, and lazy-cpp with the correct values. I don't know them.

blocks|key|1708578|text|这里有一个如何做到这一点的例子。首先，您需要使用find_program命令找到lzz程序：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1708579|find_program(LZZ_COMMAND+lzz)|code-block|syntax|javascript|1708580|这会将LZZ_COMMAND设置为编译器的路径。然后使用CMake自定义命令将LZZ文件编译为它们的C%2B%2B头文件/实现文件：|1708581|add_custom_command(
++++OUTPUT+${output}
++++COMMAND+${LZZ_COMMAND}+-o+${CMAKE_CURRENT_BINARY_DIR}+${filename})|1708582|它在当前构建目录中生成文件，以防您进行源代码外的构建。您还需要指定输出是生成的文件：|1708583|set_source_files_properties(${output}+PROPERTIES+GENERATED+TRUE)|1708584|把所有这些放在一起，你就会得到一个类似下面这样的CMakeLists.txt文件：|1708585|cmake_minimum_required(VERSION+2.8)
project(lazy_test)
find_program(LZZ_COMMAND+lzz)
function(lazy_compile+filename)
++++get_filename_component(base+${filename}+NAME_WE)
++++set(base_abs+${CMAKE_CURRENT_BINARY_DIR}/${base})
++++set(output+${base_abs}.cpp+${base_abs}.h)
++++add_custom_command(
++++++++OUTPUT+${output}
++++++++COMMAND+${LZZ_COMMAND}+-o+${CMAKE_CURRENT_BINARY_DIR}+${filename})
++++set_source_files_properties(${output}+PROPERTIES+GENERATED+TRUE)
endfunction()
lazy_compile(${CMAKE_CURRENT_SOURCE_DIR}/example.lzz)
add_executable(test+example.cpp+example.h)|1708586|最终，您可能还希望将包含路径和其他选项添加到lzz。如果您将所有惰性C%2B%2B内容放在一个模块文件中，并包含来自CMakeLists.txt的内容，它将会更干净一些。但这是基本的想法。|1708587|entityMap^0|O|C|14|3|0|0|3|B|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|19|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1A|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1B|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1C|8|@]|D|@]|E|$]]|$1|U|3|V|5|H|7|1D|8|@]|D|@]|E|$I|J]]|$1|W|3|X|5|6|7|1E|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|Z|$]]

Here is an example of how to do this... First you need to find the <code>lzz</code> program, for that use the <code>find_program</code> command:

<pre><code>find_program(LZZ_COMMAND lzz)
</code></pre>

This sets <code>LZZ_COMMAND</code> to the path of the compiler. Then use a CMake custom command to compile the LZZ file to their C++ header/implementation files:

<pre><code>add_custom_command(
 OUTPUT ${output}
 COMMAND ${LZZ_COMMAND} -o ${CMAKE_CURRENT_BINARY_DIR} ${filename})
</code></pre>

That generates the files in the current build directory, in case you do out-of-source builds. You will also need to specify that the outputs are generated files:

<pre><code>set_source_files_properties(${output} PROPERTIES GENERATED TRUE)
</code></pre>

Put that all together and you get a CMakeLists.txt file something like this:

<pre><code>cmake_minimum_required(VERSION 2.8)
project(lazy_test)
find_program(LZZ_COMMAND lzz)
function(lazy_compile filename)
 get_filename_component(base ${filename} NAME_WE)
 set(base_abs ${CMAKE_CURRENT_BINARY_DIR}/${base})
 set(output ${base_abs}.cpp ${base_abs}.h)
 add_custom_command(
 OUTPUT ${output}
 COMMAND ${LZZ_COMMAND} -o ${CMAKE_CURRENT_BINARY_DIR} ${filename})
 set_source_files_properties(${output} PROPERTIES GENERATED TRUE)
endfunction()
lazy_compile(${CMAKE_CURRENT_SOURCE_DIR}/example.lzz)
add_executable(test example.cpp example.h)
</code></pre>

You would probably also want to add include path and other options to lzz eventually. If you placed all the Lazy C++ stuff into a module file and included that from the CMakeLists.txt it would be a bit cleaner. But this is the basic idea.

blocks|key|1708611|text|我只想分享我的CMakeLists.txt，它构建在richq的脚本之上。*.cpp和*.hpp文件现在可以正确地依赖于*.lzz文件。使用source_group命令将*.lzz文件添加到项目中(这回答了absense上面的问题)，但将其与生成的文件分开。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1708612|对我来说，唯一的问题是无法为*.lzz文件编译当前文件。|1708613|cmake_minimum_required(VERSION+2.8)

PROJECT(LzzTest)

find_program(LZZ_COMMAND+lzz.exe)

#+Syntax:+
#+++add_lzz_file(<output>+<lzz+file>)
#+Adds+a+build+rule+for+the+specified+lzz+file.+The+absolute+paths+of+the+generated+
#+files+are+added+to+the+<output>+list.+The+files+are+generated+in+the+binary+dir.
#+
#+TODO:+Support+for+generating+template+files+etc.
function(add_lzz_file+output+filename)
++#+Only+process+*.lzz+files
++get_filename_component(ext+${filename}+EXT)
++if(NOT+ext+STREQUAL+".lzz")
++++return()
++endif()

++set(header_extension+"hpp")
++get_filename_component(base+${filename}+NAME_WE)
++set(base_abs+${CMAKE_CURRENT_BINARY_DIR}/${base})
++set(outfiles+${base_abs}.cpp+${base_abs}.${header_extension})
++set(${output}+${${output}}+${outfiles}+PARENT_SCOPE)

++#message("outfiles=${outfiles},+DEPENDS+${CMAKE_CURRENT_SOURCE_DIR}/${filename}")
++add_custom_command(
++++OUTPUT+${outfiles}
++++COMMAND+${LZZ_COMMAND}+
++++++-o+${CMAKE_CURRENT_BINARY_DIR}+#+output+dir
++++++-hx+${header_extension}
++++++-sl+-hl+-il+-tl+-nl+-x+#+insert+#line+commands+w/+absolute+paths
++++++-sd+-hd+-id+-td+-nd+#+don't+output+files+that+didn't+change
++++++${CMAKE_CURRENT_SOURCE_DIR}/${filename}
++++DEPENDS+"${CMAKE_CURRENT_SOURCE_DIR}/${filename}"
++)

++set_source_files_properties(${outfiles}+PROPERTIES+GENERATED+TRUE)
endfunction()

include_directories(${CMAKE_CURRENT_BINARY_DIR})

set(SOURCES
++A.lzz
++B.lzz
++main.cpp
)

foreach(file+${SOURCES})
++add_lzz_file(GENERATED_SOURCES+${file})
endforeach()

source_group(""+FILES+${SOURCES})
source_group(generated+FILES+${GENERATED_SOURCES})

add_executable(LzzTest+${SOURCES}+${GENERATED_SOURCES})|code-block|syntax|javascript|1708614|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I just wanted to share my CMakeLists.txt, which builds upon richq's script. The *.cpp and *.hpp files now properly depend on the *.lzz files. The *.lzz files are added to the project (which answers absense's question above) but kept separate from the generated files using the source_group command.

The only remaining dealbreaker for me is the inability to compile the current file for *.lzz files.

<pre><code>cmake_minimum_required(VERSION 2.8)

PROJECT(LzzTest)

find_program(LZZ_COMMAND lzz.exe)

# Syntax: 
# add_lzz_file(&lt;output&gt; &lt;lzz file&gt;)
# Adds a build rule for the specified lzz file. The absolute paths of the generated 
# files are added to the &lt;output&gt; list. The files are generated in the binary dir.
# 
# TODO: Support for generating template files etc.
function(add_lzz_file output filename)
 # Only process *.lzz files
 get_filename_component(ext ${filename} EXT)
 if(NOT ext STREQUAL ".lzz")
 return()
 endif()

 set(header_extension "hpp")
 get_filename_component(base ${filename} NAME_WE)
 set(base_abs ${CMAKE_CURRENT_BINARY_DIR}/${base})
 set(outfiles ${base_abs}.cpp ${base_abs}.${header_extension})
 set(${output} ${${output}} ${outfiles} PARENT_SCOPE)

 #message("outfiles=${outfiles}, DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/${filename}")
 add_custom_command(
 OUTPUT ${outfiles}
 COMMAND ${LZZ_COMMAND} 
 -o ${CMAKE_CURRENT_BINARY_DIR} # output dir
 -hx ${header_extension}
 -sl -hl -il -tl -nl -x # insert #line commands w/ absolute paths
 -sd -hd -id -td -nd # don't output files that didn't change
 ${CMAKE_CURRENT_SOURCE_DIR}/${filename}
 DEPENDS "${CMAKE_CURRENT_SOURCE_DIR}/${filename}"
 )

 set_source_files_properties(${outfiles} PROPERTIES GENERATED TRUE)
endfunction()

include_directories(${CMAKE_CURRENT_BINARY_DIR})

set(SOURCES
 A.lzz
 B.lzz
 main.cpp
)

foreach(file ${SOURCES})
 add_lzz_file(GENERATED_SOURCES ${file})
endforeach()

source_group("" FILES ${SOURCES})
source_group(generated FILES ${GENERATED_SOURCES})

add_executable(LzzTest ${SOURCES} ${GENERATED_SOURCES})
</code></pre>

What I'd like to do is write just Lazy C++ .lzz files and then have lzz run before a build to generate .cpp and .h files that will be built into the final application, sort of like how moc works with Qt. 

Is there any way to do this?

How do I make build rules in cmake to preprocess lazy C++ .lzz files that generate .h and .cpp files?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想要做的就是编写惰性的C++ .lzz文件，然后在构建之前运行lzz，以生成.cpp和.h文件，这些文件将被构建到最终的应用程序中，有点像moc与Qt的工作方式。有没有办法做到这一点？

问如何在cmake中创建构建规则，以预处理生成.h和.cpp文件的惰性C++ .lzz文件？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在cmake中创建构建规则，以预处理生成.h和.cpp文件的惰性C++ .lzz文件？EN