search for: plugin_llvmc_pic16base

Displaying 3 results from an estimated 3 matches for "plugin_llvmc_pic16base".

2009 Jun 23
3
[LLVMdev] llvmc for PIC16
.../example/mcc16/plugins/PIC16Base' make[1]: Leaving directory `/home/i00202/projects/llvm/tools/llvmc/example/mcc16/plugins' make[1]: Entering directory `/home/i00202/projects/llvm/tools/llvmc/example/mcc16/driver' make[1]: *** No rule to make target `/home/i00202/projects/llvm/Debug/lib/plugin_llvmc_PIC16Base.o', needed by `/home/i00202/projects/llvm/Debug/bin/mcc16'. Stop. make[1]: Leaving directory `/home/i00202/projects/llvm/tools/llvmc/example/mcc16/driver' make: *** [all] Error 1 This is with srcdir = objdir. I get the same error even when srcdir and objdir are separate. Thanks, San...
2009 Jun 18
0
[LLVMdev] llvmc for PIC16
Hi Sanjiv, 2009/6/18 Sanjiv Gupta <sanjiv.gupta at microchip.com>: > Hi Mikhail, > Thanks for your wonderful help so far. I have few more questions to ask: > > How do I modify the driver to pick tools from where the driver itself > resides, rather than from the PATH? > Do I need to write some C++ code to customize such behaviors? Yes, this is what hooks are for.
2009 Jun 18
3
[LLVMdev] llvmc for PIC16
Hi Mikhail, Thanks for your wonderful help so far. I have few more questions to ask: How do I modify the driver to pick tools from where the driver itself resides, rather than from the PATH? And how to make sure that we have same behavior on Windows as far as paths (/ Vs \) and picking up tools from the driver directory is concerned? Do I need to write some C++ code to customize such