ms build 类似于make

最新推荐文章于 2023-09-11 00:21:58 发布
原创 最新推荐文章于 2023-09-11 00:21:58 发布 · 248 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

探讨使用BinMSBuild.exe独立编译OpenVINO中security_barrier_camera_demo的方法,官方文档未提及此操作。

Bin\MSBuild.exe  Demos.sln /p:Configuration=Release /t:ecurity_barrier_camera_demo /clp:ErrorsOnly /m

openvino文档 没有提及该方法来独立编译某一个示例

 

 

在 MSBuild 编译过程中操作文件和文件夹（检查存在/创建文件夹/读写文件/移动文件/复制文件/删除文件夹）
walterlv - 吕毅
12-30 2860
本文整理 MSBuild 在编译过程中对文件和文件夹处理的各种自带的编译任务（Task）。 本文内容`Exists` 检查文件存在`MakeDir` 创建文件夹`Move` 移动文件`Copy` 复制文件`Delete` 删除文件`ReadLinesFromFile` 读取文件`WriteLinesToFile` 写入文件`RemoveDir` 删除文件夹 Exists 检查文件存在 使用 Ex...
MSBuild入门
weixin_33832340的博客
08-30 725
MSBuild是什么？ MSBuild全称（Microsoft Build Engine）,是用于构建应用程序的平台。您可能不知道它，但是如果您在使用VS做开发，那么一定时时刻刻在使用它。因为是它在背后为你管理生成你的项目文件。当新建一个项目时，注意下项目文件夹中的*.*proj文件就是为MSBuild提供的，这是个文本文件，基于XML格式，里面包含有项目所包含的文件，生成配置，输出配置等信...
MSBuild的深入认识
andycode的专栏
03-23 972
原文地址：http://knightyzj.iteye.com/blog/463157 最近在从事自动构造工作的过程中，对MSBuild本身有了一些更加深入的认识。MSBuild不仅仅是一个构造工具，应该称之为拥有相当强大扩展能力的自动化平台。 按照笔者现在的理解，MSBuild平台的主要涉及到三部分：执行引擎、构造工程、任务。其中最核心的就是执行引擎，它包括定义构造工程的规范，解释构造工程，
MS是彻底抛弃makefile了，他新一代的build system 是MS Build.
锄禾日当午
08-11 2687
MS是彻底抛弃makefile了，他新一代的build system 是MS Build.
在liunx下编译cocoapi报错(centernet) cjy@cjy-MS-7E30:~/CenterNet-master/cocoapi/PythonAPI$ make python setup.py build_ext --inplace make：python：命令未找到 make: *** [Makefile:3：all] 错误 127
07-19
如果用户已经尝试过`make`命令并报错，那么也可以直接使用`python3 setup.py build_ext --inplace`来编译。 另外，用户还提到之前尝试安装cython（`pip install cython`）后仍然报错。如果报错是关于gcc编译的，...
13:27:12 **** Incremental Build of configuration Debug_osfp_lpo for project osfp_800g_sr **** make -j8 all arm-none-eabi-objcopy -O ihex --interleave-width=32 osfp_800g_sr.elf osfp_800g_sr.hex arm-none-eabi-objcopy: interleave width must be less than or equal to interleave - byte` make[1]: *** [makefile:95: pre-build] Error 1 make: *** [makefile:63: all] Error 2 "make -j8 all" terminated with exit code 2. Build might be incomplete. 13:27:12 Build Failed. 2 errors, 0 warnings. (took 837ms) 构建失败了
最新发布
11-04
2. 检查输出是否类似： ``` GNU objcopy (xPack GNU Arm Embedded GCC x86_64) 2.36.1 ``` 3. 若版本低于 2.34，需升级工具链： - 通过 STM32CubeIDE菜单 Help > STM32CubeIDE repository 更新 ##### 步骤 3：...
[21:16:25] UnityException: No Android devices connected Make sure your device is plugged in. 21:16:251 Build completed with a result of 'Failed' in 6 seconds (6491 ms)UnityException: No Android devices connected
03-09
这部分我记得在Android开发中很常见，引用[1]中提到的Android SDK目录错误可能涉及类似的环境配置问题，但这里的问题不同，不过检查设备连接是基础步骤。 接下来，设备驱动的问题。特别是Windows系统下，有时候即使...
#!/bin/bash # Logging functions with color-coded output function log_error() { local msg="$1" if [[ -n "${msg}" ]]; then echo -e "\033[31m[ERROR] ${msg}\033[0m" fi } function log_info() { local msg="$1" if [[ -n "${msg}" ]]; then echo -e "\033[32m[INFO] ${msg}\033[0m" fi } function log_warn() { local msg="$1" if [[ -n "${msg}" ]]; then echo -e "\033[33m[WARN] ${msg}\033[0m" fi } # Execute command with error checking function run_command() { local cmd="$@" log_warn "Executing: $cmd" time eval "$cmd" local retVal=$? if [ $retVal -ne 0 ]; then log_error "Command failed with exit code $retVal: $cmd" exit $retVal else log_info "Command succeeded: $cmd" fi } # Build Android QSSI function build_android_qssi() { if [ -d "${ANDROID_QSSI_DIR}" ]; then cd "${ANDROID_QSSI_DIR}" || exit 1 unset PATH || true export PATH="${ORIGIN_ENV}" log_info "build android_qssi start" run_command "source build/envsetup.sh" run_command "lunch ${ANDROID_QSSI_TARGET}-${AND_BUILD_VARIANT}" run_command "${BASH} build.sh dist -j${MAX_JOBS} --qssi_only" log_info "build android_qssi end" else log_warn "${ANDROID_QSSI_DIR} not found, skipping!" fi } # Build Android Vendor function build_android_vendor() { if [ -d "${ANDROID_VENDOR_DIR}" ]; then cd "${ANDROID_VENDOR_DIR}" || exit 1 unset PATH || true export PATH="${ORIGIN_ENV}" log_info "build android_vendor start" run_command "source build/envsetup.sh" run_command "lunch ${ANDROID_VENDOR_TARGET}-${AND_BUILD_VARIANT}" run_command "source kernel_platform/qcom/proprietary/prebuilt_HY11/vendorsetup.sh" run_command "bash kernel_platform/build/android/prepare_vendor.sh autogvm gki" run_command "${BASH} build.sh dist -j${MAX_JOBS} --target_only" # Generate super.img if [ ! -e "${ANDROID_QSSI_DIR}/out/target/product/${ANDROID_QSSI_TARGET}/system.img" ]; then log_error "system.img must exist when generating super.img" exit 1 fi run_command "${PYTHON} vendor/qcom/opensource/core-utils/build/build_image_standalone.py --image super \ --qssi_build_path ${ANDROID_QSSI_DIR} \ --target_build_path ${ANDROID_VENDOR_DIR} \ --merged_build_path ${ANDROID_VENDOR_DIR} \ --target_lunch ${ANDROID_VENDOR_TARGET} --output_ota --skip_qiifa" log_info "build android_vendor end" else log_warn "${ANDROID_VENDOR_DIR} not found, skipping!" fi } # Build Android OTA package function build_android_ota() { if [ -d "${ANDROID_VENDOR_DIR}" ]; then cd "${ANDROID_VENDOR_DIR}" || exit 1 unset PATH || true export PATH="${ORIGIN_ENV}" log_info "build android_ota start" run_command "source build/envsetup.sh" run_command "lunch ${ANDROID_VENDOR_TARGET}-${AND_BUILD_VARIANT}" run_command "${BASH} build.sh dist --merge_only" log_info "build android_ota end" else log_error "${ANDROID_VENDOR_DIR} not found, exiting!" exit 1 fi } # Build QCOM components function build_qcom_boot() { log_info "build qcom_boot start" cd "${TEST_DEVICE_DIR}/boot" || exit 1 run_command "${PYTHON} boot_images/boot_tools/buildex.py --variant AU -r RELEASE -t Makena,QcomToolsPkg" log_info "build qcom_boot end" } function build_qcom_tz() { log_info "build qcom_tz start" cd "${TEST_DEVICE_DIR}/tz/trustzone_images/build/ms/" || exit 1 run_command "python3 build_all.py -b TZ.XF.5.0 CHIPSET=makena" log_info "build qcom_tz end" } function build_qcom_sdsp() { log_info "build qcom_sdsp start" cd "${TEST_DEVICE_DIR}/sdsp/slpi_proc/build/ms/" || exit 1 run_command "${PYTHON} ./build_variant.py makena.slpi.prod2" log_info "build qcom_sdsp end" } function build_qcom_cdsp() { log_info "build qcom_cdsp start" cd "${TEST_DEVICE_DIR}/cdsp/cdsp_proc/build/ms/" || exit 1 run_command "${PYTHON} ./build_variant.py makena.cdsp0.prod" run_command "${PYTHON} ./build_variant.py makena.cdsp1.prod" log_info "build qcom_cdsp end" } function build_qcom_adsp() { log_info "build qcom_adsp start" cd "${TEST_DEVICE_DIR}/adsp/adsp_proc/build/ms/" || exit 1 run_command "${PYTHON} ./build_variant.py makena.adsp_au.prod2" log_info "build qcom_adsp end" } function build_qcom_aop() { log_info "build qcom_aop start" cd "${TEST_DEVICE_DIR}/aop/aop_proc/build/" || exit 1 run_command "${BASH} build_makenaau.sh" log_info "build qcom_aop end" } function build_qcom_bin() { log_info "build qcom_bin start" if [ ! -d "${TEST_DEVICE_DIR}" ]; then log_error "${TEST_DEVICE_DIR} not found, exiting!" exit 1 fi cd "${TEST_DEVICE_DIR}" || exit 1 run_command "source setenv.sh" build_qcom_aop build_qcom_adsp build_qcom_cdsp build_qcom_sdsp build_qcom_boot build_qcom_tz log_info "build qcom_bin end" } # Build Android (QSSI + Vendor) function build_android_all() { log_info "build android_all start" build_android_qssi build_android_vendor log_info "build android_all end" } # Build QNX function build_qnx_only() { log_info "build qnx_only start" if [ -d "${QNX_DIR}" ]; then unset PATH || true export PATH="${ORIGIN_ENV}" cd "${QNX_DIR}/workspace/modules/bsp/apps/qnx_ap" || exit 1 run_command "source setenv_hyp710.sh --external $(pwd)/../../../../../external/sdk/qualcomm/qnx710_host -p 3R425" run_command "make" else log_warn "no qnx code found, skipping!" fi log_info "build qnx_only end" } # Build meta function build_meta() { log_info "build meta start" cd "${TEST_DEVICE_DIR}" || exit 1 if [ ! -d "${ANDROID_QSSI_DIR}" ]; then log_error "${ANDROID_QSSI_DIR} not found, exiting!" exit 1 fi if [ ! -d "${ANDROID_VENDOR_DIR}" ]; then log_error "${ANDROID_VENDOR_DIR} not found, exiting!" exit 1 fi if [ ! -d "${TEST_DEVICE_DIR}/apps_kernel" ]; then mkdir "${TEST_DEVICE_DIR}/apps_kernel" || exit 1 fi ln -fs "$(dirname "$(dirname "${ANDROID_QSSI_DIR}")")" . ln -fs "$(dirname "$(dirname "${ANDROID_VENDOR_DIR}")")" . ln -fs "${QNX_DIR}/workspace/modules/bsp/apps" . ln -fs "${KERNEL_PLATFORM_DIR}" "${TEST_DEVICE_DIR}/apps_kernel" cd "${TEST_DEVICE_DIR}/common/build" || exit 1 if [ "${GWM_V4_DV}" == "true" ]; then sed -i 's/<file_name>cluster.img<\/file_name>/<file_name><\/file_name>/g' "${TEST_DEVICE_DIR}/common/config/contents_${VARIANT}.xml" sed -i 's/<file_name>qnxres.img<\/file_name>/<file_name><\/file_name>/g' "${TEST_DEVICE_DIR}/common/config/contents_${VARIANT}.xml" sed -i 's/<file_name>vr.img<\/file_name>/<file_name><\/file_name>/g' "${TEST_DEVICE_DIR}/common/config/contents_${VARIANT}.xml" sed -i 's/<file_name>navi_buffer.img<\/file_name>/<file_name><\/file_name>/g' "${TEST_DEVICE_DIR}/common/config/contents_${VARIANT}.xml" sed -i 's/<file_name>appres.img<\/file_name>/<file_name><\/file_name>/g' "${TEST_DEVICE_DIR}/common/config/contents_${VARIANT}.xml" sed -i 's/filename=\"qnxres.img\"/filename=\"\"/g' "${TEST_DEVICE_DIR}/common/config/ufs/partition_la_ext.xml" sed -i 's/filename=\"cluster.img\"/filename=\"\"/g' "${TEST_DEVICE_DIR}/common/config/ufs/partition_la_ext.xml" sed -i 's/filename=\"navi_buffer.img\"/filename=\"\"/g' "${TEST_DEVICE_DIR}/common/config/ufs/partition_la_ext.xml" sed -i 's/filename=\"vr.img\"/filename=\"\"/g' "${TEST_DEVICE_DIR}/common/config/ufs/partition_la_ext.xml" sed -i 's/filename=\"appres.img\"/filename=\"\"/g' "${TEST_DEVICE_DIR}/common/config/ufs/partition_la_ext.xml" fi run_command "${PYTHON} build.py --flavors=${FLAVOR} --variant=${VARIANT} --st=${STORAGE}" log_info "build meta end" } # Pack qfile function pack_qfile() { log_info "build pack_qfile start" cd "${SCRIPTS_DIR}" || exit 1 run_command "${PYTHON} copy_meta_data.py --rootdir ${TOP_CODE_DIR} --output ${TOP_CODE_DIR} --variant ${VARIANT} --flavor ${FLAVOR} --storage ${STORAGE}" log_info "please get the flash img in ${TOP_CODE_DIR}/output" log_info "build pack_qfile end" } # Build userdebug (full build including QCOM, QNX, meta, and OTA) function build_userdebug() { log_info "build userdebug start" AND_BUILD_VARIANT="userdebug" build_android_all build_qnx_only build_qcom_bin build_meta build_android_ota log_info "build userdebug end" } # Build user (release version) function build_user() { log_info "build user start" unset AND_BUILD_VARIANT || true export AND_BUILD_VARIANT="user" build_android_all build_qnx_only build_qcom_bin build_meta build_android_ota log_info "build user end" } # Print help message function print_help() { log_warn "Android and QNX project paths must be replaced with actual project info!" log_info "build android qssi:\nbash build_all.sh --android_qssi" log_info "build android vendor:\nbash build_all.sh --android_vendor" log_info "build android all:\nbash build_all.sh --android_all" log_info "build qnx:\nbash build_all.sh --qnx_only" log_info "build android+qnx:\nbash build_all.sh --android_qnx" log_info "build qcom bin:\nbash build_all.sh --qcom_bin" log_info "build android ota:\nbash build_all.sh --ota\nWarning: run this after compiling all code once" log_info "build userdebug version:\nbash build_all.sh --userdebug" log_info "build user release version:\nbash build_all.sh --user" log_info "pack qfile img:\nbash build_all.sh --pack_qfile" } # Main function function main() { if [ $# -eq 0 ]; then print_help exit 0 fi # Parse arguments ARGS=$(getopt -o h --long help,pack_qfile,android_all,qcom_bin,ota,userdebug,user,android_qssi,android_vendor,qnx_only,android_qnx,dv,recompile_kernel,android_vendor_pro:,qnx_pro:,variant:,storage:,flavor:,jobs: -n "$0" -- "$@") if [ $? -ne 0 ]; then log_error "Invalid arguments. Terminating..." exit 1 fi eval set -- "${ARGS}" # Initialize flags declare -A BUILD_FLAGS while true; do case "$1" in -h|--help) print_help exit 0 ;; --android_all) BUILD_FLAGS[ANDROID_ALL]=1; shift ;; --android_qssi) BUILD_FLAGS[ANDROID_QSSI]=1; shift ;; --android_vendor) BUILD_FLAGS[ANDROID_VENDOR]=1; shift ;; --qcom_bin) BUILD_FLAGS[QCOM_BIN]=1; shift ;; --ota) BUILD_FLAGS[ANDROID_OTA]=1; shift ;; --qnx_only) BUILD_FLAGS[QNX]=1; shift ;; --recompile_kernel) export RECOMPILE_KERNEL=1; shift ;; --android_qnx) BUILD_FLAGS[ANDROID_QNX]=1; shift ;; --userdebug) BUILD_FLAGS[USERDEBUG]=1; shift ;; --user) BUILD_FLAGS[USER]=1; shift ;; --pack_qfile) BUILD_FLAGS[PACK_QFILE]=1; shift ;; --dv) export GWM_V4_DV=true; shift ;; --android_vendor_pro) ANDROID_VENDOR_TARGET="$2"; shift 2 ;; --qnx_pro) QNX_TARGET="$2"; shift 2 ;; --variant) VARIANT="$2"; shift 2 ;; --storage) STORAGE="$2"; shift 2 ;; --flavor) FLAVOR="$2"; shift 2 ;; --jobs) MAX_JOBS="$2"; shift 2 ;; --) shift; break ;; *) log_error "Unknown option: $1"; exit 1 ;; esac done # Global settings TOP_CODE_DIR=$(dirname "$(pwd)") QFILE_DIR="${TOP_CODE_DIR}/pack/qfile" FASTBOOT_DIR="${TOP_CODE_DIR}/pack/fastboot" ANDROID_QSSI_DIR="${TOP_CODE_DIR}/lagvm_qssi/LINUX/android" ANDROID_VENDOR_DIR="${TOP_CODE_DIR}/lagvm/LINUX/android" KERNEL_PLATFORM_DIR="${TOP_CODE_DIR}/lagvm_qssi/LINUX/android/kernel_platform" QNX_DIR="${TOP_CODE_DIR}/qnx" TEST_DEVICE_DIR="${TOP_CODE_DIR}/test_device" SCRIPTS_DIR="${TOP_CODE_DIR}/integration" ORIGIN_ENV="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" ANDROID_QSSI_TARGET=${ANDROID_QSSI_TARGET:-'qssi_au'} ANDROID_VENDOR_TARGET=${ANDROID_VENDOR_TARGET:-'msmnile_gvmq'} MAX_JOBS=${MAX_JOBS:-24} RECOMPILE_KERNEL=${RECOMPILE_KERNEL:-0} VARIANT=${VARIANT:-'8888la'} STORAGE=${STORAGE:-'ufs'} FLAVOR=${FLAVOR:-'8888_la'} PYTHON=${PYTHON:-'python'} BASH=${BASH:-'/bin/bash'} AND_BUILD_VARIANT=${AND_BUILD_VARIANT:-'userdebug'} # Execute builds based on flags if [ "${BUILD_FLAGS[USERDEBUG]}" == 1 ]; then build_userdebug elif [ "${BUILD_FLAGS[USER]}" == 1 ]; then build_user else if [ "${BUILD_FLAGS[ANDROID_ALL]}" == 1 ]; then build_android_all fi if [ "${BUILD_FLAGS[ANDROID_QSSI]}" == 1 ]; then build_android_qssi fi if [ "${BUILD_FLAGS[ANDROID_VENDOR]}" == 1 ]; then build_android_vendor fi if [ "${BUILD_FLAGS[ANDROID_OTA]}" == 1 ]; then build_android_ota fi if [ "${BUILD_FLAGS[QNX]}" == 1 ]; then build_qnx_only fi if [ "${BUILD_FLAGS[ANDROID_QNX]}" == 1 ]; then build_android_all build_qnx_only fi if [ "${BUILD_FLAGS[QCOM_BIN]}" == 1 ]; then build_qcom_bin fi if [ "${BUILD_FLAGS[PACK_QFILE]}" == 1 ]; then build_meta pack_qfile fi fi } # Run main main "$@" 请优化此代码实现，执行bash build_all.sh --userdebug或bash build_all.sh --user可以编译，且函数build_qcom_bin和build_meta也可以执行，且满足代码规范
06-06
但是，在我们的脚本中，我们可能也需要调用类似于m、mm等命令，或者直接调用soong_ui.bash？由于用户没有给出原始脚本，我们只能按照一般思路设计。我们假设build_qcom_bin和build_meta函数内部可能需要调用_trigger...
MAPLAB X IDE编译时报错collect2.exe: error: ld returned 1 exit status make[2]: *** [nbproject/Makefile-default.mk:435: dist/default/production/sam_c21n_ford236_txboard.X.production.hex] Error 1 make[1]: *** [nbproject/Makefile-default.mk:85: .build-conf] Error 2 make: *** [nbproject/Makefile-impl.mk:39: .build-impl] Error 2 编译 FAILED (exit value 2, total time: 761ms) 怎么回事
09-05
make[1]: *** [nbproject/Makefile-default.mk:85: .build-conf] Error 2 make: *** [nbproject/Makefile-impl.mk:39: .build-impl] Error 2 根据引用[1]中提到的类似错误（在交叉编译yaml_cpp_catkin时出现的...
make和msbuild学习笔记
hunterzone的专栏
12-30 2043
1. make Wikipedia: make >In software development, Make is a utility that automatically builds executable programs andlibraries from source code by reading files called makefiles witch specify how t
MsBuild
阿拜彩带的专栏
12-19 871
简单的一个csproj文件，可以写个类来编译一下    xmlns="http://schemas.microsoft.com/developer/msbuild/2003" >            HelloMSBuild                                                                 
MSBuild
qq_29991955的博客
09-11 1111
这个XML片段标明这是一个MSBuild工程文件，所有内容都写在Project当中。构建软件时主要需明确两类信息：编译哪些文件和采用什么构建参数。编译哪些文件会在Item中给出，构建参数（例如配置项和输出路径）会在Property中给出。MSBuild工程文件就是XML文件。1.MSBuild相关概念简介。1.1 工程文件细节。
VSCode实现cmake与msbuild一键操作
→↗允↘的博客
10-16 4468
{ "version": "2.0.0", "tasks": [ { "label": "Build", "type": "shell", "command": "mkdir build\r\ncd build\r\ncmake ..\r\nMSBuild ALL_BUILD.vcxproj -...
【整理】MSbuild
天天向上
06-22 7058
MSBuild基本概念MSBuild是什么为什么要了解MSBuild我想从MSBuild中得到什么MSBuild 基本概念项目文件属性项任务目标MSBuild 问题1.error MSB1009 MSBuild是什么 MSBuild 全称 Microsoft Build Engine，代表 Microsoft 和 Visual Studio 的新的生成平台，用于生成应用程序。此引擎为项目文件提供了一个 XML 架构，用于控制生成平台处理和生成软件的方式。 Visual Studio 会使用 MSBuild，
MSBuild简单介绍
weixin_30265171的博客
07-01 214
背景 托博客园的福，上周六，有家开发医疗行业系统的初创公司联系我，说在博客园上看到我关于WPF的几篇文章，邀请我去他们那里交流WPF相关的技术知识和心得体会。作为非大拿的我自然是受宠若惊，但对方好意相约，我便欣然前往。 诸事按过不表，在交流过程中，谈到了单独一个产品的版本控制的问题。 （以下该公司人员简称为对方） 对方：“我们用SVN，还不错。只是现在产品的版本越来越多。” 我：“怎...
MSBuild基本概念
学习，思考，记录，分享。
11-29 4283
 本博客（http://blog.youkuaiyun.com/livelylittlefish）贴出作者（三二一、小鱼）相关研究、学习内容所做的笔记，欢迎广大朋友指正！ MSBuild基本概念 1. 介绍 MSBuild内建于.Net Framework 2.0中，VS Studio 2005使用的Build就是MSBuild。MSBuild类似于Java的Ant或是.NET移植版本
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值