Unlike cmake projects that would force linking an application correctly with Torch, ICON uses GNU automate... so during compile time it will fail since libftorch.a depends on torch.... for now just use build Ftorch as shared library...
Relevant since some configurations (e.g., ICON-NWP) do build ICON as a static application (e.g., gcc -static) in order to prevent potential errors during runtime (e.g., runtime linking failure due to unfound dependencies)
Unlike cmake projects that would force linking an application correctly with Torch, ICON uses GNU automate... so during compile time it will fail since libftorch.a depends on torch.... for now just use build Ftorch as shared library...
Relevant since some configurations (e.g., ICON-NWP) do build ICON as a static application (e.g.,
gcc -static) in order to prevent potential errors during runtime (e.g., runtime linking failure due to unfound dependencies)