Before the message, you should see: "Checking for existence: ...".
Make sure the dll exists in the place C::B looks for it.
And make sure you have no spaces or special characters in the path and the dll is on the same drive as MinGW.
The DLL name contains no whitespaces or unusual characters. Putting the DLL on the same drive as MinGW isn't really going to help - but thanks anyway.
Ok, did the following:
1) Deleted the generated DLL from the previous build.
2) Build->Clean
3) Build->Build
4) ||=== Build finished: 0 errors, 13 warnings ===|
5) DLL created successfully 22/07/2010 10:43
6) Go to Build->Run and:
"It seems that this project has not been built yet. Do you want to build it now?"
Or better update your MinGW installation (I suggest TDM's build: http://tdm-gcc.tdragon.net/, or the one provided with C::B 10.5 [TDM MinGW gcc4.4]).
We don't even know if MinGW tools are used to determine whether the rebuild needs to be done, so could be a waste of time upgrading.
* * * *
Code Blocks is using a GNU makefile to build the project and displays the following in the build log box when building:
"Using makefile: makefile"
This means I can also build the project outside of Code Blocks by just calling "mingw32-make.exe".
My question was how Code Blocks determines whether to do a rebuild? Does it use the MinGW tools to check or does it just check the date of the EXE or DLL internally without MinGW? I don't believe CB is using "mingw32-make.exe" to determine whether to do a rebuild, as it would have to wait for the string "is up to date" from mingw32-make.exe and this would mean starting the build in order to deteremine whether the build was upto date or not.