User forums > Using Code::Blocks
Ctrl+Shift+F9
zabzonk:
Can't help any more (not that I was any help) I'm afraid. We appear to be using the same version of CB and the differences are:
- I'm using Win2K - as I seem to be the only person on Earth still using it, this might be a n important difference.
- I'm using TD GCC 4.4.0. You didn't mention that in your list of compilers.
Perhaps a dev could comment on whether these differences could be significant?
EDIT: And of course check that your Settings|Compiler & Debuggger|Tooolchain settings have not somehow got screwed up.
johne53:
Funnily enough it was mentioned in this thread:- http://forums.codeblocks.org/index.php/topic,11388.0.html (about 3 posts from the bottom of page 1) that compiling a single file was working okay with the gcc compiler. But I haven't managed to make it work with any other compiler :(
I wonder if it's significant that the only reports of it working so far have been with the gcc compiler selected?
Jenna:
--- Quote from: johne53 on October 30, 2009, 11:48:40 pm ---Funnily enough it was mentioned in this thread:- http://forums.codeblocks.org/index.php/topic,11388.0.html (about 3 posts from the bottom of page 1) that compiling a single file was working okay with the gcc compiler. But I haven't managed to make it work with any other compiler :(
I wonder if it's significant that the only reports of it working so far have been with the gcc compiler selected?
--- End quote ---
Does it change anything if you set your MS-compiler as default compiler ?
Or did you already try that ?
johne53:
--- Quote from: jens on October 30, 2009, 11:57:17 pm ---Does it change anything if you set your MS-compiler as default compiler ?
--- End quote ---
Woohoo..! Yes, that's it Jens. What a flash of genius! In fact, it doesn't seem to matter which compiler I select as my default, as long as the compiler is physically present on my machine. However, if the default compiler is set to some arbitrary compiler that doesn't actually exist (as it was in my case) Shift+Ctrl+F9 stops working. It stops working - even if the (project's) selected compiler does actually exist. You found it.
johne53:
I thought I'd just had a flash of inspiration myself (but it turned out to be wrong). For a moment I wondered if Ctrl+Shift+F9 might be mistakenly using the default compiler instead of the project's selected compiler. AFAICT that doesn't seem to be the case. When it works, it does seem to use the correct compiler but for some unknown reason, Ctrl+Shift+F9 seems to take the default compiler into account (whereas Ctrl+F9 and Ctrl+F11 don't).
I don't have the relevant source code so I can't see if there's a reason for this. Is there just a mistake in the strategy somewhere?
Navigation
[0] Message Index
[*] Previous page
Go to full version