Changes between Initial Version and Version 1 of Ticket #3475


Ignore:
Timestamp:
2015-09-29T09:45:05Z (9 years ago)
Author:
Martin Sjölund
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3475

    • Property Cc Adrian Pop Adeel Asghar added
    • Property Owner changed from Adeel Asghar to Martin Sjölund
    • Property Status new → accepted
    • Property Summary translateModelFMU is wrongly named → Handle source code FMU's better

  • Ticket #3475 – Description

    initial v1  
    1 translateModelFMU corresponds to the behaviour of buildModel, and should be called buildModelFMU. translateModelFMU should create a source-code FMU.
     1There are several issues that should be fixed w.r.t. FMU's:
     2
     3* translateModelFMU corresponds to the behaviour of buildModel, and should be called buildModelFMU. translateModelFMU should create a source-code FMU.
     4
     5
     6We should always create a source-code FMU first, and then update the files within it to include the binaries for one target. So something like: `buildModelFMU(M, version="2.0", targets={"linux32","linux64"})` actually corresponds to `translateModelFMU(M, version="2.0"); fmuBuildBinary("M.fmu", "linux32"); fmuBuildBinary("M.fmu", "linux64");` (and if the target cannot cross-compile for one platform, you can send the FMU to that platform and compile the sources there instead).
     7
     8When compiling a source-code FMU, two primary options are needed: linking the runtime, or compiling it yourself (necessary for targets that OpenModelica does not support; embedded targets, etc).
     9
     10We also need to know which C sources are necessary in order to compile a source-code FMU (which is different for ME and CS).