I am not sure why you didn’t receive warnings but I would say that is unimportant. I am also not sure why you have Configuration as Debug in Release but I would guess you set that in the Configuration manager.
Anyway I would suggest as noted by @laurent.berger that copying the dll’s is the wrong approach when they are on the same machine that you are building on. Your initial question was regarding another machine. In that situation the only option is to copy the dll’s to that machine.
If you are using the same machine then the recommended way is to add to the user/system path and keep the dll’s in a single location. This can present a couple of problems
- If you add to the system path then you may need to restart windows for the change to take effect.
- If you add to the user path then you will need to restart visual studio.
Both these problems can lead users to believe that this approach has not worked.
For this reason and to avoid having to restart visual studio I recommended adding the directory containing the dll’s to the working directory. This allows you to change everything lib/headers and the location of the dll without having to restart visual studio.