|
|
Re: 4DIAC - Composite Function Block [message #1809591 is a reply to message #1809587] |
Thu, 18 July 2019 15:17 |
|
To add to Martins comment you could look at subapplicatuions. Subapplications (typed, or un-typed) are flattened during deployment and therefore do not need to be compiled.
Also I would recommend to look at the work our Google Summer of Code Student Jan is doing. He is improving our dynamic type loading feature. He posted some messages with further information in our news sections as well as in the developer mailing list.
Cheers,
Alois
|
|
|
|
Re: 4DIAC - Composite Function Block [message #1809926 is a reply to message #1809921] |
Thu, 25 July 2019 18:31 |
|
I see that you are using already the setup_posix.sh. I think instead of doing the cmake setup twice I would move the stuff from the posix_setup.sh to your docker file. Then you only have one invokation of cmake and everything nicely in one place. Also as we recommend now I would put the build dir parellel to the 4diac FORTE code. so instead of cding into forte performing a 'mkdir build' in the root build dir then cd into that and invoke cmake from there. Another reason for not using our setup_posix.sh directly is that this file enables a lot what you ma not need or what you should not for a production build fo 4diac FORTE (e.g., tests). Having now the 4diac FORTE cmake config in your docker file makes you indpeendent from our build settings and gives you clearer defined builds.
But yes it should work that way. We use it similarly for our jenkins build. However we currently don't have an external module here.
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04113 seconds