- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all, we use the following version of the Softune Workbench:
- F2MC-16 Family SOFTUNE Workbench V30L35
- Cpu information file version = 19,30,01_2010.07.15
in order to produce our final output (*.mhx) to deploy on our machines.
Due to the large number of *.mhx to produce (we have several machines and models)
we developed an external automated build tool that call the Softune Workbench via command line after preparing all the necessary options. To be sure everything works we compare the .mhx file generated launching Softune manually vs the automated Tool. So far so good , we always got the same output. Recently, because space problems, we changed the compiler optimization level (General purpose optimization level) from Speed priority to Level 1. Now the outputs (*.mhx) always differ between manual and automated build. We don't understand why beacuse the automated build tool parse the project file dinamically in order to retrieve all the configurations. It seems that changing optimization level cause some hidden operation (or parameter) in softune Environment we are not able to catch. Any idea on that? Thanks for any help
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Softune toolchain has it's peculiarities, for sure. I would try this way.
Enable full build command output (here):
Compare the build output with your cmdline make, and possibly correct differences.
Don't forget the option file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Softune toolchain has it's peculiarities, for sure. I would try this way.
Enable full build command output (here):
Compare the build output with your cmdline make, and possibly correct differences.
Don't forget the option file.