编译的时候可能会出现 Not access because it is busy 的错误

[qqjmk15263]

Xmake 版本

3.0.3

操作系统版本和架构

windows10

描述问题

使用xmake来编译stm32+threadx 工程，发现在编译的时候偶尔会出现
error: cannot remove file build.objs\LL-Function-Label\mcu\stm32\debug\threadx\src__cpp_txe_semaphore_put.c.c Not access because it is busy
的错误，并且错误时提示的文件不固定，发生错误后，再次编译可能就成功

期待的结果

不报类似错误

工程配置

...

附加信息和错误日志

PS E:\Develop\Project\LL-Device\LL-PTL.threadx> xmake
[ 0%]: compiling.debug threadx\ports\cortex_m3\gnu\src\tx_misra.S
[ 1%]: compiling.debug threadx\ports\cortex_m3\gnu\src\tx_thread_context_restore.S
[ 1%]: compiling.debug threadx\ports\cortex_m3\gnu\src\tx_thread_context_save.S
[ 2%]: compiling.debug threadx\ports\cortex_m3\gnu\src\tx_thread_interrupt_control.S
[ 2%]: compiling.debug threadx\ports\cortex_m3\gnu\src\tx_thread_interrupt_disable.S
[ 3%]: compiling.debug threadx\ports\cortex_m3\gnu\src\tx_thread_interrupt_restore.S
[ 3%]: compiling.debug threadx\ports\cortex_m3\gnu\src\tx_thread_schedule.S
[ 4%]: compiling.debug threadx\ports\cortex_m3\gnu\src\tx_thread_stack_build.S
[ 4%]: compiling.debug threadx\ports\cortex_m3\gnu\src\tx_thread_system_return.S
[ 5%]: compiling.debug threadx\ports\cortex_m3\gnu\src\tx_timer_interrupt.S
[ 5%]: cache compiling.debug LL-Function-Label\main.c
[ 5%]: cache compiling.debug LL-Function-Label\startup.c
[ 6%]: cache compiling.debug threadx\src\txe_block_allocate.c
[ 6%]: cache compiling.debug threadx\src\txe_block_pool_create.c
[ 7%]: cache compiling.debug threadx\src\txe_block_pool_delete.c
[ 7%]: cache compiling.debug threadx\src\txe_block_pool_info_get.c
[ 8%]: cache compiling.debug threadx\src\txe_block_pool_prioritize.c
[ 8%]: cache compiling.debug threadx\src\txe_block_release.c
[ 9%]: cache compiling.debug threadx\src\txe_byte_allocate.c
[ 9%]: cache compiling.debug threadx\src\txe_byte_pool_create.c
[ 10%]: cache compiling.debug threadx\src\txe_byte_pool_delete.c
[ 10%]: cache compiling.debug threadx\src\txe_byte_pool_info_get.c
[ 10%]: cache compiling.debug threadx\src\txe_byte_pool_prioritize.c
[ 11%]: cache compiling.debug threadx\src\txe_byte_release.c
[ 11%]: cache compiling.debug threadx\src\txe_event_flags_create.c
[ 12%]: cache compiling.debug threadx\src\txe_event_flags_delete.c
[ 12%]: cache compiling.debug threadx\src\txe_event_flags_get.c
[ 13%]: cache compiling.debug threadx\src\txe_event_flags_info_get.c
[ 13%]: cache compiling.debug threadx\src\txe_event_flags_set.c
[ 14%]: cache compiling.debug threadx\src\txe_event_flags_set_notify.c
[ 14%]: cache compiling.debug threadx\src\txe_mutex_create.c
[ 15%]: cache compiling.debug threadx\src\txe_mutex_delete.c
[ 15%]: cache compiling.debug threadx\src\txe_mutex_get.c
[ 15%]: cache compiling.debug threadx\src\txe_mutex_info_get.c
[ 16%]: cache compiling.debug threadx\src\txe_mutex_prioritize.c
[ 16%]: cache compiling.debug threadx\src\txe_mutex_put.c
[ 17%]: cache compiling.debug threadx\src\txe_queue_create.c
[ 17%]: cache compiling.debug threadx\src\txe_queue_delete.c
[ 18%]: cache compiling.debug threadx\src\txe_queue_flush.c
[ 18%]: cache compiling.debug threadx\src\txe_queue_front_send.c
[ 19%]: cache compiling.debug threadx\src\txe_queue_info_get.c
[ 19%]: cache compiling.debug threadx\src\txe_queue_prioritize.c
[ 20%]: cache compiling.debug threadx\src\txe_queue_receive.c
[ 20%]: cache compiling.debug threadx\src\txe_queue_send.c
[ 20%]: cache compiling.debug threadx\src\txe_queue_send_notify.c
[ 21%]: cache compiling.debug threadx\src\txe_semaphore_ceiling_put.c
[ 21%]: cache compiling.debug threadx\src\txe_semaphore_create.c
[ 22%]: cache compiling.debug threadx\src\txe_semaphore_delete.c
[ 22%]: cache compiling.debug threadx\src\txe_semaphore_get.c
[ 23%]: cache compiling.debug threadx\src\txe_semaphore_info_get.c
[ 23%]: cache compiling.debug threadx\src\txe_semaphore_prioritize.c
[ 24%]: cache compiling.debug threadx\src\txe_semaphore_put.c
[ 24%]: cache compiling.debug threadx\src\txe_semaphore_put_notify.c
[ 25%]: cache compiling.debug threadx\src\txe_thread_create.c
[ 25%]: cache compiling.debug threadx\src\txe_thread_delete.c
[ 25%]: cache compiling.debug threadx\src\txe_thread_entry_exit_notify.c
[ 26%]: cache compiling.debug threadx\src\txe_thread_info_get.c
[ 26%]: cache compiling.debug threadx\src\txe_thread_preemption_change.c
[ 27%]: cache compiling.debug threadx\src\txe_thread_priority_change.c
[ 27%]: cache compiling.debug threadx\src\txe_thread_relinquish.c
[ 28%]: cache compiling.debug threadx\src\txe_thread_reset.c
[ 28%]: cache compiling.debug threadx\src\txe_thread_resume.c
[ 29%]: cache compiling.debug threadx\src\txe_thread_suspend.c
[ 29%]: cache compiling.debug threadx\src\txe_thread_terminate.c
[ 30%]: cache compiling.debug threadx\src\txe_thread_time_slice_change.c
[ 30%]: cache compiling.debug threadx\src\txe_thread_wait_abort.c
error: cannot remove file build.objs\LL-Function-Label\mcu\stm32\debug\threadx\src__cpp_txe_semaphore_put.c.c Not access because it is busy

[star-hengxing]

如果在公司，可能跟加密软件有关

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

If you are in a company, it may be related to encryption software

[qqjmk15263]

如果在公司，可能跟加密软件有关

电脑是个人电脑应该没有安装加密软件，有安装杀毒软件

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

If you are in a company, it may be related to encryption software

The computer is a personal computer, there should be no encryption software installed, and there is antivirus software installed

[waruqi]

这种通常跟 xmake 没啥关系，文件被其他进程占用了，导致访问失败。要么就是毒软正在扫这个文件。

[qqjmk15263]

这种通常跟 xmake 没啥关系，文件被其他进程占用了，导致访问失败。要么就是毒软正在扫这个文件。

删除了几个会监控文件的程序后，确实是发生的概率小了很多，可不可以将这些文件的删除放到编译完以后，不然经常会出现后台放着编译，编译到一半就自动报错，然后停止编译

[qqjmk15263]

这种通常跟 xmake 没啥关系，文件被其他进程占用了，导致访问失败。要么就是毒软正在扫这个文件。

删除了几个会监控文件的程序后，确实是发生的概率小了很多，可不可以将这些文件的删除放到编译完以后，不然经常会出现后台放着编译，编译到一半就自动报错，然后停止编译

项目中有大量很小的.c文件，编译这些文件的速度很快，经常在编译这些文件的时候出现这个问题，导致编译停止，一次完整编译经常需要点击好几次才能完成

[waruqi]

不能，如果真是被其他进程干扰了，光这里处理没啥用，编译过程中，会有各种文件读写删除，只要有一个地方失败，都会跪。没法根本解决问题。

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

This usually has nothing to do with xmake, the file is occupied by other processes, resulting in access failure. Or Du Ruo is scanning this file.

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

This usually has nothing to do with xmake, the file is occupied by other processes, resulting in access failure. Or Du Ruo is scanning this file.

After deleting several programs that monitor files, the probability of occurrence is indeed much smaller. Can you delete these files after compilation? Otherwise, there will be often a background to compile, and an error will be automatically reported after halfway through compilation, and then the compilation will be stopped.

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

This usually has nothing to do with xmake, the file is occupied by other processes, resulting in access failure. Or Du Ruo is scanning this file.

After deleting several programs that monitor files, the probability of occurrence is indeed much smaller. Can you delete these files after compilation? Otherwise, there will be often a background to compile, and an error will be automatically reported after halfway through compilation, and then the compilation will be stopped.

There are a large number of small .c files in the project, and the speed of compiling these files is very fast. This problem often occurs when compiling these files, causing the compilation to stop. A complete compilation often requires several clicks to complete.

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

No, if it is really interfered by other processes, there is nothing to do with processing here. During the compilation process, there will be various file read, write and deleted files. As long as there is a place that fails, you will kneel down. There is no way to solve the problem fundamentally.

[qqjmk15263]

不能，如果真是被其他进程干扰了，光这里处理没啥用，编译过程中，会有各种文件读写删除，只要有一个地方失败，都会跪。没法根本解决问题。

或者说能不能配置让生成的像 __cpp_txe_semaphore_put.c.c 这类文件不删除，等到clean的时候再删除，只要能顺利编译完整个工程，不中断就行

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

No, if it is really interfered by other processes, it is useless to process it here. During the compilation process, there will be various file read, write and deleted files. As long as there is a place that fails, you will kneel down. There is no way to solve the problem fundamentally.

Or can you configure the generated files like __cpp_txe_semaphore_put.c.c not deleted, and then delete them when clean. As long as the complete project can be successfully compiled and not interrupted.