Add source code FMU to integration and validation tests

[lausdahl]

It would be good if you could add the C code FMUs under testing

• the script integration-test.sh exports and runs with out own small COE
• the script validate.sh compiles the FMU checker and checks against that

You need to add an extra script to compile the FMU after export (this was not needed for the tool wrapper)

[bandurvp]

Compilation of the source code FMU must take place locally on the build server and not upload to the FMU build server.

[bandurvp]

@lausdahl, it does not look like the overture-fmu build on Jenkins is fetching the latest fmu-tester. Could you please confirm whether this is true?

[lausdahl]

I think it is ok as is. but if you want to change commit then you have to go to ```bash cd testing/fmu-tester git pull cd .. git add fmu-tester git commit -m “bumped up fmu-tester” git push ```

…

On 23 Aug 2017, at 17.25, Victor Bandur ***@***.***> wrote: @lausdahl <https://github.com/lausdahl>, it does not look like the overture-fmu build on Jenkins is fetching the latest fmu-tester. Could you please confirm whether this is true? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#59 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACdMOh7o1Sx8VDvl0saQ225m9Akq0A8aks5sbERQgaJpZM4NIuc9>.

[bandurvp]

So the Git submodule command doesn't pull in the latest commit?

[lausdahl]

no thats not how it works. The specific commit that the submodule is located as is recorded in a file in the place where the submodule will be checked out. If you brows there on github you will see the repo name and the commit id. The submodule command clones the repo and checkouts the specified commit. To change it you have to manually do as I showed above.