solved Linking "foreign" library - not build on running system ?

[Vaclav_]

I keep running into snags using Linux "autotools " generated code. Would this work? 1. Build required C++ library on host architecture and link it to the "build" system? I am successfully using Target Communication Framework - Agent - to "connect" from build system to host . Uses TCP. I used "post-processing" long time ago and I was thinking if that or pre-processing could be used to "add" the library link before the main process is done. Just a thought. I do not know to to "link" across network during program compilation / linking. 2. Could I just import / copy the correct architecture library from the host system to build system and just link it normally? I am going to try "scp" Linux command to copy the C++ library from the host to build system. Is there anything special why this "scp" copy would not work? SOLUTION Used option 2 - scp /rcp to copy library build on ARM system to similar folder on X86. Linked to it the usual way. Linker accepted the file format , no problems. Test run on ARM "host" and works as expected. Cheers

[Lost User]

It is not clear what the actual problem is, and why you cannot build the library in the same way that you build the rest of the system. Linking a library to an application should work if both sides have been built to the same target architecture.