Why does CVI2013 build two executables?

[Wolfgang]

Hello NI,

many things have changed with the move to the clang compiler, and accordingly some questions arise...

For example, I realized that building a debug executable creates two (identical) executables, one located in my project folder, and one in the cvibuild.project/debug folder... Why?

[tstanley]

CVI has been doing that for a long time.  I've always assumed that it builds the copy in the Debug folder and when done copies it to the root project directory to run it.  Maybe NI can comment.

[Wolfgang]

---

@tstanley wrote:

CVI has been doing that for a long time. 

---

Ah, making a fool of myself... But thank you for pointing it out!

[LuisG · Accepted solution]

Yes, tstanley is correct. I believe the change happened in version 2010, when the use of build configurations became widespread. It was important to place all the build output files, including the .exe, inside the configuration folder, so that they wouldn't blap each other. At the same time, CVI needed to continue honoring the Target Settings>>Application file setting, and so it copies the .exe to the location specified in the target settings after building it in configuration folder

Luis