2014:hash_define_hell_in_multi-platform_embedded_programming
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| 2014:hash_define_hell_in_multi-platform_embedded_programming [2013/11/05 11:55] – created jonjagger | 2014:hash_define_hell_in_multi-platform_embedded_programming [2016/06/11 14:05] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| **Description**: | **Description**: | ||
| A lot of projects face the challenge that the source code has to be compiled for different targets. Either the same SW has to be compiled for different CPUs or slightly different code has to be compiled for the same CPU. In some projects the same binary code has to run on several different HW platforms, but behave differently. In this presentation we look at different ways to solve these problems. The presentation is based on the experience of a 8 year project with 15 different build targets.\\ | A lot of projects face the challenge that the source code has to be compiled for different targets. Either the same SW has to be compiled for different CPUs or slightly different code has to be compiled for the same CPU. In some projects the same binary code has to run on several different HW platforms, but behave differently. In this presentation we look at different ways to solve these problems. The presentation is based on the experience of a 8 year project with 15 different build targets.\\ | ||
| - | \\ | ||
| \\ | \\ | ||
| \\ | \\ | ||
| + | JJ: Tore writes - if there are not enough 45 min sessions I am sure I could drag my session out to a 90 min speak. | ||
2014/hash_define_hell_in_multi-platform_embedded_programming.1383652513.txt.gz · Last modified: 2016/06/11 14:05 (external edit)