search for: mcjite

...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 almost > certainly not what you'd want. Whatever makes the symbols from the .a available to the MCJITed code would work for me, but I can't tell if that's better done inside or outside of MCJIT itself. Robin -- Robin Sommer * Phone +1 (510) 722-6541 * robin at icir.org ICSI/LBNL * Fax +1 (510) 666-2956 * www.icir.org/robin

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

OK, so in the old implementation you linked a module against the archive before passing it to MCJIT? I'm not familiar with the llvm::Linker interface, so I hope someone else will jump in an address that. I can think of a way to solve this inside MCJIT, but it is almost certainly not what you'd want. -Andy -----Original Message----- From: Robin Sommer [mailto:robin at icir.org] Sent: