rm -r -f not working

General questions regarding the usage of CodeLite
ultrajunkie
CodeLite Enthusiast
Posts: 15
Joined: Mon Mar 20, 2017 11:05 pm
Genuine User: Yes
IDE Question: C++
Contact:

rm -r -f not working

Post by ultrajunkie »

I have 2 different computers working with the same workspace on a network drive. The share is connected via network drive mapping using the same server user (admin). Both machines are running the same WIn 11 version.

On no. 1, I can call "Clean", and it will clean the build as expected.

On no. 2, the call returns with

rm: cannot remove '../build-Debug_DLL/myapp': Directory not empty
mingw32-make[1]: *** [myapp.mk:480: clean] Error 1
mingw32-make: *** [Makefile:8: clean] Error 2

I checked the permissions for the directory, and it shows a partial write protection, but I can't find from where it comes.

Any ideas?

ultrajunkie
CodeLite Enthusiast
Posts: 15
Joined: Mon Mar 20, 2017 11:05 pm
Genuine User: Yes
IDE Question: C++
Contact:

Re: rm -r -f not working

Post by ultrajunkie »

With the help of Microsoft Copilot (I hate to say that... :roll: ) I found the issue!

On one machine, I have a tool chain for Raspberry installed, and the path was included in the path variable for my user. As a consequence, Codelite was using the rm version (8.21) in this tool chain rather than its own (8.32). After I deleted the tool chain in Codelite AND the path entries in the path variable, deleting worked without any further issue.

Following conclusion:

  1. all tools, that Codelite is using during the make process should be configurable at least per compiler set, better per project (with the use of the general settings as default)
  2. As default, the tools coming with Codelite should be used, and other versions should be displayed as options
  3. Codelite should somehow work with its own version of path. It should take the system path information but resort it based on the tool chain used. I'm not sure if e.g. the correct include files and libraries are used for the Raspberry tool chain if in the path the directory for the normal GNU 15.1 compiler comes first.
Post Reply