New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify static linking #438

Open
modelica-trac-importer opened this Issue Oct 17, 2018 · 2 comments

Comments

Projects
None yet
4 participants
@modelica-trac-importer

modelica-trac-importer commented Oct 17, 2018

Reported by cbertsch on 18 Jun 2018 09:01 UTC
Clarification regarding static linking for 2.0.1 bugfix release.
See #313 for changes in FMI 3.0
To be clarified:
"self contained" is not clearly defined.

Define "self contained" that FMUs may not dependend on something external of the FMU (all DLLs and other resources must be contained in the FMU, exception: CS FMUs with needsTool-XML-Tag. As this will not work generally for runtime systems, it is recommended to always link runtimes statically (for Windows Visual Studia use option /MT)


Migrated-From: https://trac.fmi-standard.org/ticket/438

@andreas-junghanns

This comment has been minimized.

Contributor

andreas-junghanns commented Oct 23, 2018

FMI Design Meeting (Roanne, Siemens PLM, Oct, 2018): We called a poll on the question:
"Should we allow external dependencies for static (compile time) and dynamic (runtime) linking of FMUs (even if we strongly discourage such practices) and if yes, proper dependency documentation must be available in the modelDescription.xml (see source-code FCP for 3.0)?"
Agree: (11)
Disagree: (6)
Abstain: (2)

@KarlWernersson

This comment has been minimized.

Collaborator

KarlWernersson commented Nov 13, 2018

Can we get a good solution here for 2.0.1 or should we leave it for 3.0?

@KarlWernersson KarlWernersson removed the 2.0.1 label Nov 13, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment