You don't need newer builds to make things work. I've just added more logging. 13.12 is perfectly fine and could do the job.
I found a possible problem; setting compiler to "No Compiler" fails to work on my suggestion of command only.
It works great with the mingw gcc as the compiler; but, it does give the nothing to be done message.
Running target pre-build steps
CMD /c dir
Volume in drive E is Backup
Volume Serial Number is 2A96-F81C
Directory of E:\OpenSourceCode\Test\script_only
03/25/2014 03:23 PM <DIR> .
03/25/2014 03:23 PM <DIR> ..
03/25/2014 03:23 PM 1,019 script_only.cbp
1 File(s) 1,019 bytes
2 Dir(s) 1,312,088,064 bytes free
-------------- Build: script in script_only (compiler: GNU GCC Compiler)---------------
Target is up to date.
Process terminated with status 0 (0 minute(s), 0 second(s))
0 error(s), 0 warning(s) (0 minute(s), 0 second(s))
Attached my cbp projects 7zipped.
custom Makefile also fails if "no compiler" is used.
All this tested on CB 13.12 running on Windows 7 32-bit
Tim S.
[attachment deleted by admin]
Hm, are you sure you've archived the correct project. I see simple gcc based project.
I attached the one(s) that works; not the one(s) that fails.
Just change the compiler to no compiler and it fails to work under CB 13.12.
I attached a custom makefile using "no compile" to this message.
"makefile_only_bad - make_only": The compiler's setup (*No Compiler*) is invalid, so Code::Blocks cannot find/run the compiler.
Probably the toolchain path within the compiler options is not setup correctly?! (Do you have a compiler installed?)
Goto "Settings->Compiler...->Global compiler settings->*No Compiler*->Toolchain executables" and fix the compiler's setup.
Skipping...
Nothing to be done (all items are up-to-date).
Tim S.