Forum : Ride IDE
Original Post
| Post Information | Post |
|---|---|
|
October 25, 2011 - 5:03pm
|
Whenever I go in debug, all source files get recompiled - even if none was changed. I have loaded and installed the latest revision of the tool and it still behaves the same. Any idea why and how to fix? |
Hi,
We would like to help you as quickly as possible on this issue, but we need to have more informations about the problem before we can help further.
In order to understand the issue you are facing, we need the following information about your configuration:
- Version of Windows: At a command prompt type the following command: "systeminfo.exe", which gives you a system report. We need the full "Operating System" and "Version" from the report.
- Version of Ride7 and RKit that you are using. You can get these from the Ride7 "Help | About" dialog box.
Please check from the Raisonance downloads page at http://www.mcu-raisonance.com/mcu_downloads.html that you are using the latest version of the tools.
Concerning your particular problem:
- Provide the steps you followed to raise the error.
- The precise error message you received, and which tool produced it. If possible, a screenshot of the message (using the PrtScr keyboard key) is helpful.
- Does the problem occur when using the examples given with Ride7 (from the Ride7 installation directory, default being "C:\Program Files\Raisonance\Ride\Examples\")?
You may encounter a specific issue related to 64-bit Windows. If you have a 64-bit system, just read this http://forum.raisonance.com/viewtopic.php?id=3080 that describes the problem and its solution.
Another known issue is about some Windows versions that do not have the script engine properly registered. You can check this from http://forum.raisonance.com/viewtopic.php?id=3296.
Please let us know when the problem has been solved satisfactorily.
Best Regards
The problem is very simple: clicking the debug icon ALWAYS causes the entire project to get entirely rebuilt, recompiling every single source file, even if no change was made to any source file.
PC is running XP
OS Name: Microsoft Windows XP Professional
OS Version: 5.1.2600 Service Pack 3 Build 2600
Ride7 version 7.34.0250
RKit-ARM for Ride 7 version 1.36.11.0285
Thanks
Hi,
This may be caused by a problem in Ride7's internal database.
What you can do is to remove all the interemediate project files (.o, .ctx, .dbi, .xdb...). Just keep your source files, your .rprj and .rapp files.
Rebuild your project and give it a try.
If the problem persists, can you test one of the provided examples (in examples\ARM\REva\...) and see if the problem also happens?
Best Regards,
I have the same problem as cosmapa. Additionally, each time I press F9 all the source files in the project are compiled. In previous version of Ride7 only the file that was modified was compiled. It is very problematic.Removing the files (.o, .ctx, .dbi, .xdb...). doesn't help. My project contains many source files and compiling them each time I click debug consumes much time.
Hi Kekon,
Can you zip your whole project (including all intermediate files such as .o, .lst, .map etc) and sent it to ? We will experiment with it and try to understand the issue.
BTW ensure that you are using the latest versions from http://www.mcu-raisonance.com/mcu_downloads.html.
Best Regards,
Cleaning the project directory worked for me. However, I had to quit and restart Ride
I had the same re-building problem but I solved it. The solution is, compiling projects under C:/ directory. Basicly, move your project folder, under C:/ and compile again. Make proccess will work properly.
usinergy, I'm not sure what you mean. Where was your project before you moved it? Are you saying you had it on a different drive letter, e.g., D:, or in a subdirectory of C:\, and you had to move the project to the root of C:?
I found the solution to my own issue like this. It was related to two things:
1. I set up my project so the application location was in a subfolder of the root of the project -- the .rprj file was in, say Firmware\Test, but the .rapp file was in Firmware\Test\Demo. This is different from the default, which places both in the root of the project. I did this so that I could have multiple applications within one project, and keep their output folders separate from each other.
2. I changed the Output Directory of the Demo application (Application Options -> Directories -> Output Directory) to .\obj instead of $(ApplicationDir). I did this to ensure the output files didn't clog up the Demo folder.
The fix was to change the Output Directory to $(ApplicationDir)\obj. Strangely, the .obj files end up in the same place (Firmware\Test\Demo\obj), but now the build system works right -- it only builds changed files.
Check modification date of the source files in your project, maybe some file is from the future.