Skip to content
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

Revisit section on source code distrubution #699

Closed
t-sommer opened this issue Jan 2, 2020 · 1 comment
Closed

Revisit section on source code distrubution #699

t-sommer opened this issue Jan 2, 2020 · 1 comment
Assignees
Labels
Milestone

Comments

@t-sommer
Copy link
Collaborator

@t-sommer t-sommer commented Jan 2, 2020

Is this still true/required with the new BuildConfiguration element?

If default options of the compiler are sufficient, it might then be possible to automatically process such source code FMUs.
An exporting tool should give documentation on how to build an executable, either via a documentation file and/or via a template makefile for a particular platform, from which a user can construct the makefile for his/her target platform.

@t-sommer t-sommer added the documents label Jan 2, 2020
@t-sommer t-sommer added this to the v3.0 milestone Jan 2, 2020
@andreas-junghanns

This comment has been minimized.

Copy link
Contributor

@andreas-junghanns andreas-junghanns commented Jan 3, 2020

The idea of source code FMUs is to be as platform independent as possible.
We realise this is not entireley possible, but shipping platform dependent makefiles is as good as shipping platform binaries - what would be the point?
We want to ship code so that we can reach unknown platforms using unknown compilers, ideally.
Therefore, we should try to build as much flexibility into the standard as possible to define as much as needed, but not to require more.
Since the compile/link stuff is differently tricky on different platforms, this would benefit from a discussion in a group.

Note also: The long-term archival people are also tending towards source code FMUs. Their requirements make it even more obvious that we cannot know target platforms/compilers/linkers.

@t-sommer t-sommer added task and removed Berlin2020 labels Feb 21, 2020
andreas-junghanns pushed a commit to andreas-junghanns/fmi-standard that referenced this issue Feb 22, 2020
t-sommer pushed a commit that referenced this issue Feb 22, 2020
see #782
@t-sommer t-sommer closed this Feb 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.