Is it possible to force Eclipse CDT to build a project created by CMake without considering the freshness of resources?

Question

I found myself in an odd pattern using Eclipse. I have a project that depends on resources that are not properly accounted for in the eclipse project, so if I only update the title depending on it, Eclipse refuses to build on command, apparently because it does not consider it necessary. As a result, I end up constantly adding one place to the file and saving to get the CDT to place my bets.

Although it would be possible to integrate dependencies into project parameters, the project is sometimes overwritten by the CMake automatic generation tool (which I have no interest in fixing), which overwrites the configuration and requires me to reconfigure the dependencies again and again.

What I would like to do is simply just tell Eclipse that it should ignore what it thinks should happen and obey the build command and let the underlying system do the job (determine what should and should ) t will be built).

TL DR:

• Eclipse CDT is trying to determine whether to create by observing the freshness of files
• It tracks correctly configured dependencies
• I don’t want to configure dependencies because the project is often overwritten by CMake when adding files to the project

- , CDT ?

Answer 1

, ( ), , Eclipse , , -, .

, "" ( → " " ), . effectivelly . , , .

Answer 2

make :

FORCE:

%.o : %.cpp FORCE
    $(CXX) -c $(CXXFLAGS) $< -o $@

FORCE - , , . , FORCE , .

Answer 3

Are you using the internal Eclipse builder? Because when you use the external builder setting, I do not experience any problems that you talked about. Even when editing some files outside of Eclipse, the assembly will work, even though Eclipse is completely unaware of the changes.