You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, git revision of libcloudphxx is stored in a header file.
Software that dynamically loads libcloudphxx (e.g. UWLCM) needs to be recompiled after new version of libcloudph++ is installed in order to output proper git revision of libcloudph++.
This could be improved if libcloudph++ defined a function returning the git revision.
The text was updated successfully, but these errors were encountered:
I concur this would be useful, but rather to implement a "you are dynamically linking with different version of libcloudph++ than UWLCM was compiled against" warning (or error).
The point is that when compiling UWLCM with libcloudph++ headers, some constants or even more elaborate logic gets compiled into the UWLCM binaries (e.g., p_vs(T) function). Now, imagine libcloudph++ gets a new implementation of p_vs(T) - then the case definition would be inconsistent with what is happening while time-stepping.
Currently, git revision of libcloudphxx is stored in a header file.
Software that dynamically loads libcloudphxx (e.g. UWLCM) needs to be recompiled after new version of libcloudph++ is installed in order to output proper git revision of libcloudph++.
This could be improved if libcloudph++ defined a function returning the git revision.
The text was updated successfully, but these errors were encountered: