search for: lmylib

...%s", str); } mylib.h: #ifndef MY_LIB_HEADER #define MY_LIB_HEADER void printString(char* X); #endif /////////////////////////////////////// Normally in C++ I do this: g++ -fPIC -c mylib.c g++ -shared -o libmylib.so mylib.o (and after that : g++ -Wall -g -o prog.exe prog.c -I./ -lmylib -L./ LD_LIBRARY_PATH=/home/mylinux/Desktop/test ./prog.exe) My program I compile like this: $ llvm-as -f prog.ll $ llc -march=x86-64 prog.bc -f but I have error after: $ g++ -o prog prog.s -I./ -L./ -lmylib /tmp/ccLAh0mg.o: In function `main': asd.bc:(.text+0xd): undefined reference to `pri...

On Thu, Jun 18, 2009 at 3:57 PM, Jules Jacobs<julesjacobs at gmail.com> wrote: > How can I call C++ libraries (LLVM & Qt for example) from a language that's > implemented on top of LLVM? You can call them the same way a C++ file compiled with llvm-g++ would call them. Essentially, it's complicated enough that you probably don't want to do it for any interface of

Hi, How can I call C++ libraries (LLVM & Qt for example) from a language that's implemented on top of LLVM? Thanks, Jules -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090619/4621508b/attachment.html>

...on the bitcode before generating the native binary. Here's whats happening: If the source code compilation process builds a static library (.a archive file), I need a means to link the `.a' file statically into the application. So if the original statement was: gfortran file.o -L somedir -lmylib -o file then my modified compilation process would have to deal with file.o and libmylib.a to generate the binary `file'. Now, all files essentially contain bitcode (file.o and object files inside libmylib.a). So the pseudo-code would look like: -- QUOTE -- For all input files passed to comp...

...ore generating the native binary. Here's whats happening: If the > source code compilation process builds a static library (.a archive file), I > need a means to link the `.a' file statically into the application. So if > the original statement was: > gfortran file.o -L somedir -lmylib -o file > then my modified compilation process would have to deal with file.o and > libmylib.a to generate the binary `file'. Now, all files essentially contain > bitcode (file.o and object files inside libmylib.a). So the pseudo-code > would look like: > -- QUOTE -- > For all...

...ry. Here's whats happening: If > the > > source code compilation process builds a static library (.a archive > file), I > > need a means to link the `.a' file statically into the application. So if > > the original statement was: > > gfortran file.o -L somedir -lmylib -o file > > then my modified compilation process would have to deal with file.o and > > libmylib.a to generate the binary `file'. Now, all files essentially > contain > > bitcode (file.o and object files inside libmylib.a). So the pseudo-code > > would look like: >...

Hi, I'm using compiler-rt to build the library to replace libgcc. How can I disable -lgcc being added and passed to the linker? When I use: "clang -ccc-gcc-name arm-cross-g++ hello.c -Lmypath -lmylib -v" -lgcc is always added: "...gcc/arm-none-linux-gnueabi/4.6.1/collect2 ... /tmp/hello-Pj9QxO.o -lgcc ..." How can I disable or override libgcc from the command line? Thanks. -Liang

Sorry, at what step do you need archive? llc emits binary, it does not perform any linking, thus it does not need anything except the input bytecode file. Then during linking you can link whatever archives of binaries you want. 2011/9/13 Ashay Rane <ashay.rane at tacc.utexas.edu>: > Thats correct. But using llc becomes a problem when I have archives (.a > files). I could, in theory,

Thats correct. But using llc becomes a problem when I have archives (.a files). I could, in theory, extract its contents to a tempdir and then use llc and link but just wondering if there is a more elegant solution. Ashay On Mon, Sep 12, 2011 at 3:00 PM, Dmitry N. Mikushin <maemarcus at gmail.com>wrote: > Ashay, > > If I understand correctly, in hw.o you would have llvm