Dev-C++ didn't show/start the DOS window
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
Menu
▾
▴
Hello,
I use Dev-C++ v4.9.9.2 under Windows2000SP4.
Two weeks ago I tryed some c-programms and it works well.
Now I will compile and run a new c-programm and I didn't get the DOS window.
I never changed something.
After new installation and getchar() or somthing like that didn't work.
Any idea what is happend?
Thank you in advance for informations.
Regards,
Matti
Hi,
Dev-C++ can compile and save my programm as .exe. That's perfect.
I can start the programm with Windows-Explorer and in the Dos-Console.
I think Dev-C++ lost the "link" to the Dos-Console to start the programm.
Unfortunatly I can't find something in the options.
The source-code is not the problem.
Regards,
Matti
When you are asking for people to help you, and you are asked for information, it is a VERY bad idea to ignore or dismiss their requests.
Clifford knows FAR better than you do what he is looking for - so - post your code and the associated log.
One of the basic principles of remote problem resolution is that the information you provide should give your helper enough data to duplicate what you are seeing. General descriptions, like you insist on providing, provide context, but no data.
Wayne
Sorry, here is the code:
include <stdio.h>
include <stdlib.h>
int main ()
{
int ch;
for (ch=32;ch<=255;ch++) printf("\n%i %c", ch, ch);getchar();
return 0;
}
-----------Source-Code-End------------------------------
How can the sourcecode be wrong, when I can start the exe-file in Windows-Explorer or in the Dos-Console?
Now it's interessting, what do mean, what is wrong and why Dev-C++ didn't run the programm ([F9] or (CTRL+[F10])) in the DOS-Console.
Looking forward for your information.
Regards,
Matti
Pulling hair out.
Please pay attention to what you are asked for!
Clifford, and later I asked you to post your compile log.
Pay attention!
Your compile log tells us a lot about how your code was compiled - it is on the tab labeled 'Compile Log' - and the right mouse button brings up the copy menu.
Wayne
Here is the Compile log:
Compiler: Default compiler
Executing gcc.exe...
gcc.exe "J:\study\Beispiel02.c" -o "J:\study\Beispiel02.exe" -ansi -I"C:\Dev-Cpp\include" -L"C:\Dev-Cpp\lib"
Execution terminated
Compilation successful
Hopefully this helps.
Regards,
Matti
Hello,
first: Thank you for helping.
"Do not create a console window" = No
Now I saw a mistake with my directory. I posted following:
Compiler: Default compiler
Executing gcc.exe...
gcc.exe "J:\study\Beispiel02.c" -o "J:\study\Beispiel02.exe" -ansi -I"C:\Dev-Cpp\include" -L"C:\Dev-Cpp\lib"
Execution terminated
Compilation successful
But my work directory, with the problem, is:
J:\Studium\GPI\GPI 02\Heftbeispiele\Beispiel02.c
I think the space between GPI 02 is THE problem:
J:\Studium\GPI\GPI02\Heftbeispiele\Beispiel02.c
No Dos-window:
Compiler: Default compiler
Executing gcc.exe...
gcc.exe "J:\Studium\GPI\GPI 02\Heftbeispiele\Beispiel02.c" -o "J:\Studium\GPI\GPI 02\Heftbeispiele\Beispiel02.exe" -ansi -I"C:\Dev-Cpp\include" -L"C:\Dev-Cpp\lib"
Execution terminated
Compilation successful
I created a new directory:
J:\study\programming\c\test 01\examples\
Here is everything perfect:
Compiler: Default compiler
Executing gcc.exe...
gcc.exe "J:\study\programming\c\test 01\examples\Beispiel02.c" -o "J:\study\programming\c\test 01\examples\Beispiel02.exe" -ansi -I"C:\Dev-Cpp\include" -L"C:\Dev-Cpp\lib"
Execution terminated
Compilation successful
But I'm absolutly sure the I worked from beginning on in this directory:
J:\Studium\GPI\GPI 02\Heftbeispiele\
I do not understand what is happend, but in the changed directory is everything OK.
Regards,
Matti
But your new directory contains a space too! If you concluded that it was causing a problem in the first place, why did you do it again!
How did you manage to post a 'false' log!? How can a copy & paste go that wrong!? Had you posted the real log, you would have had an answer first go. Had you read the "read first" thread, you would not even have needed to ask.
Clifford
If you read through the history of this board - you will see a number of cases
like yours that feature a statement of the general form "But it used to work"
with respect to spaces. (I refer to this in the "Please read" thread)
I really wish I knew why that happens - it is truelly evil as it lulls people
into thinking "That old fool Wayne doesn't know what he's talking about when
he says not to use spaces in paths to code" - the fool part is fine, but
experience says the latter will bit you in the but at some point.
Way to stick with it
Wayne
There are a number of possible reasons, but we cannot help you without more information. You are asking us to take your word for a number of things when you could just post an example of the code you are running and the Compile Log of its build and we could see for ourselves. That fact is that at least some of what you are saying cannot be true, otherwise it would work wouldn't it?
... note that the log is not just useful when you have build errors. If shows how your code has been built, and with what options.
test
OK, sorry about the test, work network is weird
Now, under
Tools:Compiler Options:Settings:Linker
is an option called
"Do not create a console window"
check what that is set for.
Wayne
Having the full path "J:\study\" in the name is unusual, and is probably confusing Dev-C++. Beats me how you managed to get it to do that. It will look for the .exe in the current working directory, and since you have an explicit path, that the CWD is not likely to be the same.
You are not using the project facility. I recommend that you do. This is likely to solve the problem. File->New->Project.
Clifford
I take that back. Having the path there is normal (I always use a project where if the source and project are in the same file you would not normally have a full path). Sorry.
Using a project is still a good idea however, it gives you far more control and may solve your problem.
Clifford
Clifford makes a good point. One thing that a project keeps you away from is
having global changes that one makes impact an unrelated coding activity.
For example, in running certain graphics programs, there are reasons for
NOT wanting to have a console window pop up. So, you turn it off. Then,
later, after a few days have passed, you do something new - and you forget
you changed it, and you pull a few hairs out.
I have done stupid stuff like that, more than once...
Wayne