Subsequent ceedling invocations fail to execute if the vendor lib files have read-only permissions

[adamatom]

First off, thanks for this project. I have been using it for many years now. It is really exciting to see Ceedling 1.0 and all of the fixes and features it comes with.

As part of ceedling's build process, it copies the unity, cmock, and cexception source files into :build_root:/vendor from the UNITY_LIB_PATH, CMOCK_LIB_PATH, and CEXPCEPTION_LIB_PATH. That occurs in lib/ceedling/configurator_setup.rb, here.

I have found that if the source files found in UNITY_LIB_PATH, CMOCK_LIB_PATH, and CEXPCEPTION_LIB_PATH have read-only permissions, then FileUtils.cp_r will preserve them when it makes the recursive copy. The first ceedling invocation will succeed, but subsequent invocations will fail with a permission error because the files already exist as read-only in my :build_root:/vendor:
🧨 EXCEPTION: Permission denied @ rb_sysopen - ./build/ceedling/vendor/unity/src/./unity.h

I can hack around this with a command hooks:

:plugins:
  :enabled:
    - command_hooks

:command_hooks:
    :executable: chmod
    :arguments:
      - "-R"
      - "+w"
      - "./build/ceedling/vendor"
  :post_error:
    *fixup_vendor_dir

Would it be reasonable to change configurator_setup.rb to chmod the files after it has copied them?

[twaldecker]

I also have this permission error for build/test/backtrace.gdb:

$ rm build/test/backtrace.gdb
$ ceedling test:all
...
-----------------------
❌ OVERALL TEST SUMMARY
-----------------------
TESTED:  59
PASSED:  58
FAILED:   1
IGNORED:  0

---------------------
BUILD FAILURE SUMMARY
---------------------
Unit test failures.


Ceedling operations completed in 8.63 seconds
$ ceedling test:all
🚧 Loaded project configuration from working directory.
 > Using: /home/thomas/projekte/xxx/ceedling/project.yml
 > Working directory: /home/thomas/projekte/xxx/ceedling

🧨 EXCEPTION: Permission denied @ rb_sysopen - build/test/backtrace.gdb
$ ls -la build/test/backtrace.gdb
-r--r--r-- 1 thomas thomas 81 Aug 13 11:58 build/test/backtrace.gdb

I "fixed" it before for the unity.c file by running chmod -R u+w build