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 we use a mix of dynamic linking with passL: -lc10 -ltorch_cpu and static linking with {.link.}
We want to cleanly use dynamic linking for starter as the linker step is very slow and c10/torch have no static lib provided, at least on Linux.
So we want either dynlib or the passL strategy but without any {.link.}.
Furthermore we need to check where we need the library o minimize path issues, is it nimble bin or does it have a lib folder?
The text was updated successfully, but these errors were encountered:
Currently we use a mix of dynamic linking with
passL: -lc10 -ltorch_cpu
and static linking with {.link.}We want to cleanly use dynamic linking for starter as the linker step is very slow and c10/torch have no static lib provided, at least on Linux.
So we want either dynlib or the passL strategy but without any
{.link.}
.Furthermore we need to check where we need the library o minimize path issues, is it nimble
bin
or does it have alib
folder?The text was updated successfully, but these errors were encountered: