Community
Participate
Working Groups
Build ID: I20070601-1539 + CDT 4.0 RC3 Steps To Reproduce: 0. ensure that workspace auto-refresh is disabled 1. create an HelloWorld project (gcc) 2. add some command line flags producing some extra files (eg: -dl -dA -dn) 3. compile with external make builder: all generated files (*.c.<int>.<ext>) are immediately visible to the user in the output directory 4. switch to the internal builder, clean and rebuild project: only the .o/.exe files are visible. The internal builder probably assumes that it knows all output files, but then you need to manually refresh the output directory to see the other files generated by the compiler. This is somehow related to bug 163652 which requests a way to disable the automatic refresh on build (here we want to force the refresh). Maybe the internal builder should at least explicitly perform a refresh in order to behave the same way as the external make builder ...
+1. I am running into this with the MSVC toolchain as well since it generates a number of extra build artifacts as a result of the build. It would seem reasonable to refresh the entire output directory. I have a feeling it would be difficult to tell the build system about every possible output file (which I believe it is using to do the refresh now).
+1. I agree that specifying every build artifact would be difficult (we have files that can be arbitrarily named) and a full refresh would do the trick for us.
+1 . A full refresh would work for us as well.
