• Add conan support
• Allow loading FMUs from URLs
• Misc

• Fix wrong project CMake version
• Make logger private

• Add missing spdlog dependency for target FMI4cpp
• Fix spdlog/fmt issues on windows

No API changes from v0.5.0

• FMU resources used by tests and examples are now bundled with the code
• Removed spdlog headers. They must now be installed separately
• Don't build fmu_driver by default

A lot of breaking changes.

Some highlights:

• Non fmi2 related or otherwise re-usable code has been moved out of the fmi2 namespace.
• Added FMI4CPP_USING_VCPKG CMake option. This should be off when building on linux with apt-get dependencies.
• Exposed modelDescriptionParser. The modelDescription.xml can now be parsed by clients without instantiating an FMU.
• Added logging API

Several minor fixes, refactoring and minor API additions. Should be backwards compatible with v0.4.0.

Adds fmu_driver command line tool tool and crosscheck utility.

Add support for wrapping ME models as CS ones

In order to prepare for future support for fmi3, changes include:

• Return bool instead of status on fmi functions. The actual status can be retrieved by slave->getLastStatus()
• Introduce fmi4cpp::Status as a replacement for fmi2Status.
• Don't use fmi2 typedefs in headers that (in the future) should be common for both fmi2 and fmi3.

++

Various updates and refactoring to make FMI4cpp compatible with FMU-proxy.

Most noteworthy is a major change to the API where init is removed from FmuInstance. Users must now replace this call with the three functions setupExperiment, enterInitializationMode and exitInitializationMode (in that order). The reason being that the old init function made it impossible to set start values as intended.

Fix issues with 0.2.0 release and some refactoring

• Boost headers are no longer public
• Made attributes easier to instantiate
• Made ModelVariables and ModelStructure (smart) pointers
• various refactoring

This release brings some major API and stability fixes.
Most noteworthy is that XML parsing is now an implementation detail.
Changes are not backwards compatible with 0.1.0.