![]() |
Telelogic Rhapsody (steve huntington) | ![]() |
Topic Title: Memory footprint Topic Summary: Created On: 10-Jul-2006 09:41 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello
What is the approx. memory footprint (ROM), that OXF will use? Thanks, Denker |
|
![]() |
|
![]() |
|
I'd think that would depend alot on the platform you're compiling for and the various settings for number of timers, etc.... My release version of my entire product for windows is 600K, and I'd think most of that is application. Maybe create a project with a simple object and build it in release mode for your target?
|
|
![]() |
|
![]() |
|
Can somebody tell me the approximate memory footprint if I would use IDF instead of OXF framework? How much ROM can be saved?
I would appreciate any approximate numbers that you have experienced during your developments - both for IDF and OXF thanks, Michael |
|
![]() |
|
![]() |
|
I have absolutely no clue how much footprint the OXF will generate, but I have can supply you some information about the IDF.
The following text is quoted from a slide of the essential tool training for Rhapsody in C.
I hope this helps you a bit. I remember that we asked for the OXF footprint size too during the training, but we haven't got a really good answer. At least nothing which was worth writing down, and I can't remember it anymore. Yours, Bernhard |
|
![]() |
|
![]() |
|
It's me again, I just realized that I can supply you with some values for IDF and OXF on a Windows PC with gcc under Cygwin as compiler.
The values are from a very simple project with one main object and some nested subobjects. It contains almost zero logic, just a few timers and printf's (less than 10 lines of code). IDF project executable file: 112KB OXF project executable file: 1,35MB Additional information: The IDF works without container classes and RiCString, they can be included but I haven't done this (default is: not included). I can not supply you with code size for my target system, because there is an RTOS linked together with the Rhapsody-code. So the size of the image isn't correct. Yours, Bernhard EDIT: These values are for a debug-build. For release build see next posting. Edited: 7-Feb-2008 at 12:46 by Bernhard Gassner |
|
![]() |
|
![]() |
|
Bernhard,
thanks for sharing your experiences. However, if somebody else also can provide some details about actual footprint sizes in their projects, I'd greatly appreciate it. Michael |
|
![]() |
|
![]() |
|
The values are from a very simple project with one main object and some nested subobjects. It contains almost zero logic, just a few timers and printf's (less than 10 lines of code). IDF project executable file: 112KB OXF project executable file: 1,35MB I mixed something up with that values. I just took one of the already existing simple testing projects on my hard disk and checked the file sizes. But I forgot to set the compiler from 'debug' to 'release' first. The correct values for release-build are: IDF project executable file: 112KB OXF project executable file: 1,26MB Animation was deactivated in any of the listed cases. Sorry for the mistake. Bernhard Edited: 7-Feb-2008 at 12:47 by Bernhard Gassner |
|
![]() |
|
![]() |
|
Thanks for your update Bernhard.
Speaking of Release mode, I'd have a related question: I tried to set my configuration (just for "Microsoft", not a specific target yet) from Debug to Release mode, but all I get are following errors at make-time: Building ------------ DefaultComponent.exe ------------ Executing: "...\Rhapsody\Share\etc\msmake.bat" DefaultComponent.mak build Setting environment for using Microsoft Visual Studio 2005 x86 tools. Linking DefaultComponent.exe LINK : fatal error LNK1181: cannot open input file '...\Rhapsody\Share\LangC\lib\MsoxfR.lib' NMAKE : fatal error U1077: '"...\MS Visual Studio 8\VC\BIN\link.exe"' : return code '0x49d' Stop. So basically it seems that I miss the file "MsoxfR.lib" (which I physically don't have on my hard disk). Unfortunately, I also couldn't find any hints in Rhapsody documentation about Release mode. If someone has a clue what I am missing/doing wrong here or can point me to relevant documentation, it'd be very helpful! Thanks, Michael |
|
![]() |
|
![]() |
|
Hello Michael,
In order to create an OXF library in Release mode, you have to edit your makefile. For example, in Microsoft makefile "msbuild.mak" (<Rhapsody>\Share\LangCpp\), you have to specify BUILD_SET=RELEASE instead of BUILD_SET=DEBUG. You have then to rebuild your OXF library : ..\etc\msmake.bat msbuild.mak I hope it will help you. Eric |
|
![]() |
|
![]() |
|
@Eric:
Thanks a lot - could 100 % solve my problem - I was not aware of that circumstance because for IDF in release mode rebuilding was not necessary. @Bernhard: just for the record - did you measure the release-build sizes just by comparing the created executables (e.g. DefaultComponent.exe), right? |
|
![]() |
|
![]() |
|
just for the record - did you measure the release-build sizes just by comparing the created executables (e.g. DefaultComponent.exe), right? That's correct, yes. |
|
![]() |
|
![]() |
|
Hello,
do you also have some numbers for the RAM consumption? Anyone there with experience in the usage of the Willert framework or the new static C framework? thanks Christian |
|
![]() |
|
![]() |
|
sorry, I have absolutely no information about the RAM consumption.
|
|
![]() |
Telelogic Rhapsody
» Rhapsody Category » Rhapsody
»
Memory footprint
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.