Warning: Project not compiled (A: not yet...)
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
Menu
▾
▴
In my case it happens after copying a project into a new directory instead of
creating a new project. It seems to have problems with the resource file dates
and times. The progress box no longer shows the resource compiler being
activated. The compiled resource file appears as having been generated AFTER
the executable. The IDE is unable to Run the executable, much less debug it. I
am using a custom maintained makefile and code libraries in another directory
but changing that does not solve the problem. It reappeared after making
changes to the resource included file. The executable begun acting erratically
afterwards. This question has arose before but there is no definitive answer.
The problem seems to rely solely in the IDE and file times logic, not in the
makefile or the compiler itself.
Nice launch in! Are we supposed to know what it is exactly that happens!?
Ignore the progress box, the Compile Log text details every command executed
and its output. You should post that. The progress box may not correctly parse
the output of a custom makefile since it expects the output from a Dev
generated makefile.
Dev-C++ by default assumes that the executable name is the same as the project
name and is in the same folder as the project folder. If neither of these are
the case, you have to set a custom output file.
When using a custom makefile, the IDE has exactly no control over the build,
so this seems unlikely. Does the build work if you run teh make from the
command line? (You'll need to add c:\dev-cpp\bin to the PATH environment
variable to make that work.
Note that when you moved the project, if the custom makefile has direct paths
rather than relative paths, it may be looking at the wrong files. Deleting or
renaming the original project directory (if it still exists) may be a good
idea, since it will then fail if there are dependencies on the original files.
Also you will need to do a clean build; however Dev-C++ "Rebuild All" command
may not work for your custom makefile unless it uses the same target
conventions as Dev-C++'s generated makefiles, so you may need to do this
manually or from teh command line. Again you can check what actually
happened via the "Compile Log".
In the end, the place to start is the "Compile Log". Without that it is all
guess work.
Clifford
I copy the whole directory under the projects root, then rename it, when I
want to have a quick project or test.
It was showing the windress compilation anyway...
The IDE is unable to Run the executable
See below
I use a derivation of the original autogenerated makefile, only manage it
differently.
All relative paths are unchanged because I just add another node in the same
directory tree node
Not at ALL!!! 8D The idea is to make some tests in a project without having to
do much effort to revert to the previous version. Actually what I delete is
the copy project.
The problem manifests also after clean builds, which is why it is so
exasperating
I opted to manage the autogenerated makefiles to have more control but it
respects its structure
It is STILL a problem in the IDE logic...
I unified all names: new directory, executable, executable name in makefile
(based on auto generated one), overriden executable file in project options.
Now it says: Warning: source not compiled.
But a -Rebuild all- command correctly compiles all C++ files. This left
lingering the PREVIOUS project name IN the project.dev file and showing it
in the IDE...
And it worked! A lot of effort though. I had to RENAME all references to the
previous name IN the .dev file and make them match the directory name! The
.dev file contains the self file name and The Name and the name in folders.
Ideally these unnecessary dependencies should not count when compiling (from
another directory). The problem is incomplete logic in the IDE. I had to
change a total of 12 times the same name in dialog boxes and files to make the
IDE Run the executable again.
I am not surprised that that might fail. The .dev file is plain text, open it
up and see if there are any references to the original folder in it and rename
them. Then rebuild all.
I had to read to the end to find out I'd wasted my time typing that! (all
above and below). I think "It works" rather deserves a place near the top of
the post to avoid people wasting time on your behalf!
Woah! Keep your hair on; this suggestion was not intended as a solution, but
rather part of the investigation. You loose nothing if you temporarily rename
it or back it up and delete it. In the absence of information given, I am
trying to find out more; you don't have to assist in investigating your own
problem, but I may just give up trying. The same was true of the building from
the command line suggestion which you have chosen not to comment on. If you do
not engage in teh investigation and report back, why are you here?
How can you conclude that when you have relinquished the IDE of all control by
using a custom build. The IDE simply launches make.exe with your make file. If
the build fails, the IDE has no responsibility.
This is becoming very painful! Why don't you just let us have all the
diagnostic information available and post the "Compile Log" text in full as
you are asked in the "PLEASE READ BEFORE POSTING A QUESTION" thread? I am
sorry but I though that it might be obvious that that was what was needed when
I mentioned it the first time.