search for: linkinlibrary

On Wed, Sep 25, 2013 at 17:14 +0000, you wrote: > What API did you use in 3.2? llvm::Linker used to have a method LinkInLibrary(). My understanding is that there's a larger reorganisation of the linking process going on but I haven't found a straight-forward replacement for that method yet. I might be missing something though. Or perhaps I could even just reuse some code from that old method; need to look at that....

Hi all, is there a way to link a native static library (.a) into code that runs through MCJIT? I was able to do it with LLVM 3.2, but it seems the API has changed and maybe was removed? Thanks, Robin -- Robin Sommer * Phone +1 (510) 722-6541 * robin at icir.org ICSI/LBNL * Fax +1 (510) 666-2956 * www.icir.org/robin

What API did you use in 3.2? I've never tried this, but I think it's probably possible. -Andy -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Robin Sommer Sent: Tuesday, September 24, 2013 9:37 PM To: llvmdev at cs.uiuc.edu Subject: [LLVMdev] Linking static archives with MCJIT? Hi all, is there a way to link a native

...[mailto:robin at icir.org] Sent: Wednesday, September 25, 2013 12:02 PM To: Kaylor, Andrew Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Linking static archives with MCJIT? On Wed, Sep 25, 2013 at 17:14 +0000, you wrote: > What API did you use in 3.2? llvm::Linker used to have a method LinkInLibrary(). My understanding is that there's a larger reorganisation of the linking process going on but I haven't found a straight-forward replacement for that method yet. I might be missing something though. Or perhaps I could even just reuse some code from that old method; need to look at that....

On Wed, Sep 25, 2013 at 19:23 +0000, you wrote: > OK, so in the old implementation you linked a module against the > archive before passing it to MCJIT? Yes, I used a Linker instance to link together a number of my own modules and a static library, and then get a single new LLVM module out of that to hand over to MCJIT. > I can think of a way to solve this inside MCJIT, but it is