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?
Currently we use a mix of dynamic linking with
passL: -lc10 -ltorch_cpuand 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 nimblebinor does it have alibfolder?