make modules 和 make modules_install depend

本文详细解析了makemodules命令的作用,即编译指定为M的硬件驱动,以及如何通过modules_install将这些驱动安装到指定的文件系统根目录下的/lib/modules目录,并生成依赖关系,确保modprobe加载时能正确处理依赖驱动。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

make modules 和 make modules_install depend:
make modules:把指定为M的硬件驱动,进行编译
modules_install INSTALL_MOD_PATH=/media/wyz/rootfs,
把指定为M的驱动安装到/media/wyz/rootfs下面的/lib/modules目录下面,
/media/wyz/rootfs指的是文件系统根目录

depend -a 就会把/lib/modules目录下面的驱动生成依赖关系,modprobe加载的时候,就可以先加载依赖驱动

你根本就没有真正意识到你错了哪里!,你看看-v输出详情 cat@lubancat:~/work/lvgl/demo_linux_port_sdl$ cmake --build ./build -v /usr/bin/cmake -S/home/cat/work/lvgl/demo_linux_port_sdl -B/home/cat/work/lvgl/demo_linux_port_sdl/build --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /home/cat/work/lvgl/demo_linux_port_sdl/build/CMakeFiles /home/cat/work/lvgl/demo_linux_port_sdl/build/CMakeFiles/progress.marks /usr/bin/make -f CMakeFiles/Makefile2 all make[1]: Entering directory '/home/cat/work/lvgl/demo_linux_port_sdl/build' /usr/bin/make -f CMakeFiles/rk3588_sdl2.dir/build.make CMakeFiles/rk3588_sdl2.dir/depend make[2]: Entering directory '/home/cat/work/lvgl/demo_linux_port_sdl/build' cd /home/cat/work/lvgl/demo_linux_port_sdl/build && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /home/cat/work/lvgl/demo_linux_port_sdl /home/cat/work/lvgl/demo_linux_port_sdl /home/cat/work/lvgl/demo_linux_port_sdl/build /home/cat/work/lvgl/demo_linux_port_sdl/build /home/cat/work/lvgl/demo_linux_port_sdl/build/CMakeFiles/rk3588_sdl2.dir/DependInfo.cmake --color= Dependee "/home/cat/work/lvgl/demo_linux_port_sdl/build/CMakeFiles/rk3588_sdl2.dir/DependInfo.cmake" is newer than depender "/home/cat/work/lvgl/demo_linux_port_sdl/build/CMakeFiles/rk3588_sdl2.dir/depend.internal". Dependee "/home/cat/work/lvgl/demo_linux_port_sdl/build/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/home/cat/work/lvgl/demo_linux_port_sdl/build/CMakeFiles/rk3588_sdl2.dir/depend.internal". Scanning dependencies of target rk3588_sdl2 make[2]: Leaving directory '/home/cat/work/lvgl/demo_linux_port_sdl/build' /usr/bin/make -f CMakeFiles/rk3588_sdl2.dir/build.make CMakeFiles/rk3588_sdl2.dir/build make[2]: Entering directory '/home/cat/work/lvgl/demo_linux_port_sdl/build' [ 50%] Building C object CMakeFiles/rk3588_sdl2.dir/Src/main.c.o /usr/bin/cc -DLV_CONF_INCLUDE_SIMPLE=1 -I/home/cat/software/install_dir/lv_port_linux/include -I/home/cat/software/install_dir/lv_port_linux/include/lvgl -I/usr/include/SDL2 -Wall -Wextra -std=gnu11 -o CMakeFiles/rk3588_sdl2.dir/Src/main.c.o -c /home/cat/work/lvgl/demo_linux_port_sdl/Src/main.c [100%] Linking C executable rk3588_sdl2 /usr/bin/cmake -E cmake_link_script CMakeFiles/rk3588_sdl2.dir/link.txt --verbose=1 /usr/bin/cc -Wall -Wextra CMakeFiles/rk3588_sdl2.dir/Src/main.c.o -o rk3588_sdl2 -lSDL2 /home/cat/software/install_dir/lv_port_linux/lib/liblvgl.a -lpthread -lm -ldl 你的确找到了lvgl静态库的绝对路径地址/home/cat/software/install_dir/lv_port_linux/lib/liblvgl.a,但是你没有加-L来直接连接
06-25
cmake_minimum_required(VERSION 3.0.2) project(oryxbot_cruise_ex) ## Compile as C++11, supported in ROS Kinetic and newer # add_compile_options(-std=c++11) ## Find catkin macros and libraries ## if COMPONENTS list like find_package(catkin REQUIRED COMPONENTS xyz) ## is used, also find other catkin packages find_package(catkin REQUIRED COMPONENTS ar_pose ar_track_alvar_msgs arm_controller geometry_msgs rei_robot_cruise relative_move roscpp ) ## System dependencies are found with CMake's conventions # find_package(Boost REQUIRED COMPONENTS system) ## Uncomment this if the package has a setup.py. This macro ensures ## modules and global scripts declared therein get installed ## See http://ros.org/doc/api/catkin/html/user_guide/setup_dot_py.html # catkin_python_setup() ################################################ ## Declare ROS messages, services and actions ## ################################################ ## To declare and build messages, services or actions from within this ## package, follow these steps: ## * Let MSG_DEP_SET be the set of packages whose message types you use in ## your messages/services/actions (e.g. std_msgs, actionlib_msgs, ...). ## * In the file package.xml: ## * add a build_depend tag for "message_generation" ## * add a build_depend and a exec_depend tag for each package in MSG_DEP_SET ## * If MSG_DEP_SET isn't empty the following dependency has been pulled in ## but can be declared for certainty nonetheless: ## * add a exec_depend tag for "message_runtime" ## * In this file (CMakeLists.txt): ## * add "message_generation" and every package in MSG_DEP_SET to ## find_package(catkin REQUIRED COMPONENTS ...) ## * add "message_runtime" and every package in MSG_DEP_SET to ## catkin_package(CATKIN_DEPENDS ...) ## * uncomment the add_*_files sections below as needed ## and list every .msg/.srv/.action file to be processed ## * uncomment the generate_messages entry below ## * add every package in MSG_DEP_SET to generate_messages(DEPENDENCIES ...) ## Generate messages in the 'msg' folder # add_message_files( # FILES # Message1.msg # Message2.msg # ) ## Generate services in the 'srv' folder # add_service_files( # FILES # Service1.srv # Service2.srv # ) ## Generate actions in the 'action' folder # add_action_files( # FILES # Action1.action # Action2.action # ) ## Generate added messages and services with any dependencies listed here # generate_messages( # DEPENDENCIES # ar_track_alvar_msgs# geometry_msgs # ) ################################################ ## Declare ROS dynamic reconfigure parameters ## ################################################ ## To declare and build dynamic reconfigure parameters within this ## package, follow these steps: ## * In the file package.xml: ## * add a build_depend and a exec_depend tag for "dynamic_reconfigure" ## * In this file (CMakeLists.txt): ## * add "dynamic_reconfigure" to ## find_package(catkin REQUIRED COMPONENTS ...) ## * uncomment the "generate_dynamic_reconfigure_options" section below ## and list every .cfg file to be processed ## Generate dynamic reconfigure parameters in the 'cfg' folder # generate_dynamic_reconfigure_options( # cfg/DynReconf1.cfg # cfg/DynReconf2.cfg # ) ################################### ## catkin specific configuration ## ################################### ## The catkin_package macro generates cmake config files for your package ## Declare things to be passed to dependent projects ## INCLUDE_DIRS: uncomment this if your package contains header files ## LIBRARIES: libraries you create in this project that dependent projects also need ## CATKIN_DEPENDS: catkin_packages dependent projects also need ## DEPENDS: system dependencies of this project that dependent projects also need catkin_package( # INCLUDE_DIRS include # LIBRARIES oryxbot_cruise_ex # CATKIN_DEPENDS ar_pose ar_track_alvar_msgs arm_controller geometry_msgs rei_robot_cruise relative_move roscpp # DEPENDS system_lib ) ########### ## Build ## ########### ## Specify additional locations of header files ## Your package locations should be listed before other locations include_directories( include ${catkin_INCLUDE_DIRS} ) ## Declare a C++ library # add_library(${PROJECT_NAME} # src/${PROJECT_NAME}/oryxbot_cruise_ex.cpp # ) ## Add cmake target dependencies of the library ## as an example, code may need to be generated before libraries ## either from message generation or dynamic reconfigure # add_dependencies(${PROJECT_NAME} ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS}) ## Declare a C++ executable ## With catkin_make all packages are built within a single CMake context ## The recommended prefix ensures that target names across packages don't collide add_executable(${PROJECT_NAME}_node src/oryxbot_cruise_ex.cpp src/oryxbot_task.cpp ) ## Rename C++ executable without prefix ## The above recommended prefix causes long target names, the following renames the ## target back to the shorter version for ease of user use ## e.g. "rosrun someones_pkg node" instead of "rosrun someones_pkg someones_pkg_node" # set_target_properties(${PROJECT_NAME}_node PROPERTIES OUTPUT_NAME node PREFIX "") ## Add cmake target dependencies of the executable ## same as for the library above add_dependencies(${PROJECT_NAME}_node ${${PROJECT_NAME}_EXPORTED_TARGETS} ${catkin_EXPORTED_TARGETS}) ## Specify libraries to link a library or executable target against target_link_libraries(${PROJECT_NAME}_node ${catkin_LIBRARIES} ) ############# ## Install ## ############# # all install targets should use catkin DESTINATION variables # See http://ros.org/doc/api/catkin/html/adv_user_guide/variables.html ## Mark executable scripts (Python etc.) for installation ## in contrast to setup.py, you can choose the destination # catkin_install_python(PROGRAMS # scripts/my_python_script # DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION} # ) ## Mark executables for installation ## See http://docs.ros.org/melodic/api/catkin/html/howto/format1/building_executables.html # install(TARGETS ${PROJECT_NAME}_node # RUNTIME DESTINATION ${CATKIN_PACKAGE_BIN_DESTINATION} # ) ## Mark libraries for installation ## See http://docs.ros.org/melodic/api/catkin/html/howto/format1/building_libraries.html # install(TARGETS ${PROJECT_NAME} # ARCHIVE DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION} # LIBRARY DESTINATION ${CATKIN_PACKAGE_LIB_DESTINATION} # RUNTIME DESTINATION ${CATKIN_GLOBAL_BIN_DESTINATION} # ) ## Mark cpp header files for installation # install(DIRECTORY include/${PROJECT_NAME}/ # DESTINATION ${CATKIN_PACKAGE_INCLUDE_DESTINATION} # FILES_MATCHING PATTERN "*.h" # PATTERN ".svn" EXCLUDE # ) ## Mark other files for installation (e.g. launch and bag files, etc.) # install(FILES # # myfile1 # # myfile2 # DESTINATION ${CATKIN_PACKAGE_SHARE_DESTINATION} # ) ############# ## Testing ## ############# ## Add gtest based cpp test target and link libraries # catkin_add_gtest(${PROJECT_NAME}-test test/test_oryxbot_cruise_ex.cpp) # if(TARGET ${PROJECT_NAME}-test) # target_link_libraries(${PROJECT_NAME}-test ${PROJECT_NAME}) # endif() ## Add folders to be run by python nosetests # catkin_add_nosetests(test)怎么修改
06-29
模块一般用来支持那些不经常使用的功能。例如,通常情况下你仅使用拨号网络,因此网络功能并不是任何时候都需要的,那么就应该使用可装入的模块来提供这个功能。仅在你进行拨号联接的时候,该模块才被装入。而在你断掉连接的时候它会被自动卸下。这样会使内核使用内存的量最小,减小系统的负荷。 当然,那些象硬盘访问这样时时刻刻都需要的功能,则必须作在内核里。如果你搭一台网络工作站或 web服务器,那么网络功能是时刻都需要的,你就应该考虑把网络功能编译到内核里。另外一个方法是在启动的时候就装入网络模块。这种方法的优点是你不需要重新编译内核。而缺点是网络功能不能特别高效。 按照以上的原则,我们首先列出一张清单,看看 kernel 中哪些选项是非有不可的,也就是说,这些东西是必须被编译到内核中的。将那些非必需的模块剔除到内核以外。 第一个是root所在的硬盘配置。 哪果您的硬盘是IDE接口,就把 ide 的选项标记下来。如果是SCSI接口,请把您的接口参数及 SCSI id 记标下来。 第二个是选择使用哪一个文件系统。 Linux的默认文件系统是是 ext2 ,那么就一定要把它标记下来。如果机器中还其它的操作系统,如win98或windows NT,您还会可能选择FAT32或NTFS的支持,不过后面你可以通过手工加载的方式来加入新的模块支持。 第三个是选择Linux所支持的可执行文件格式。这里有两种格式可供选择: elf:这是当前Linux普遍支持的可执行文件格式,必须编译到内核中 。 a.out: 这是旧版的Linux的可执行文件各函数库的格式,如果你确认肯定用不到这种格式的可执行文件,那么就可以不把它编译到内核当中。 以上这些内容,是必须要编译到内核中的。其它的内容凡是所有选项中m提示的,都选择m,这样可以通过手工的方式添加该模块。 ** Loadable module support*Enable loadable module support (CONFIG_MODULES) [Y/n/?]Set version information on all symbols for modules (CONFIG_MODVERSIONS) [N/y/?]Kernel daemon support (e.g. autoload of modules) (CONFIG_KERNELD) [Y/n/?] 分别回答 Y,N,Y 。其中 CONFIG_KERNELD 的 default 值是 N, 所以要注意选择Y。 make config 完后,仍旧是 make dep; make clean。 接下来要 make zlilo 或 make zImage。 然后 make modules ; make modules_install 。完成之后,就编译出一个没有调入多余模块的一个“干净的”内核映像文件了。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值