Frank Bergmann

And with that we come full circle :) ... @sebastiandev originally was using of course C++17, which made the library available pretty much only on windows. I've tried with several...

@yannikschaelte thank you ... unfortunately i'm still having some issues. So theoretically all the information is already present in the data after a run of the pypesto notebook, if I...

will do ... ideally those plotting functions would also be fine with taking data frames directly (or the petab_problem).

I believe the first thing to do would be to change from the `set` command to the `option`. That is instead of: ``` set(EXPAT_MSVC_STATIC_CRT OFF CACHE BOOL "Use /MT flag...

In the end my problem went away using the option command instead: ```diff diff --git a/expat/CMakeLists.txt b/expat/CMakeLists.txt index 6797fd43..7a392c8e 100644 --- a/expat/CMakeLists.txt +++ b/expat/CMakeLists.txt @@ -150,7 +150,7 @@ mark_as_advanced(EXPAT_LARGE_SIZE) option(EXPAT_MIN_SIZE...

> > > In the end my problem went away using the option command instead: > > So that is disabling caching of the option? Before I understand the full...

> > No .. it just means, that currently a user defined value of `EXPAT_MSVC_STATIC_CRT ` is just overridden by the `set` command. using the `option` statement, the value is...

> @fbergmann I have done some research on the behavior and difference of `option(..)` and `set(.. CACHE ..)` now. For my local experiment, my `CMakeLists.txt` was this: > > ```cmake...

That test is incomplete, please add `grep MSVC_STATIC CMakeCache.txt` after the cmake run. When just setting the variable, the cache variable defined later will override it. In my case by...

I obviously prefer a): * it is consistent with the other options defined * it resolves the (to me surprising change of the variable) * for me it does not...