llvm dev - Jun 2009 - [LLVMdev] llvmc for PIC16

Mikhail Glushenkov wrote:
> Hi Sanjiv,
>
> 2009/6/15 Sanjiv Gupta <sanjiv.gupta at microchip.com>:
>   
>> Hi Mikhail,
>> How do you build mcc16 executable?
>>     
>
> This should work:
>
> $ cd $LLVM_DIR/tools/llvmc/examples/mcc16
> $ make
>
>   
I configure llvm into a separate directory from source.
When I do the steps you mentioned in the source directory, this is what 
I get.

[i00171 at rhino mcc16]$ make
../../../../Makefile.common:61: ../../../../Makefile.config: No such 
file or directory
../../../../Makefile.common:69: /Makefile.rules: No such file or directory
make: *** No rule to make target `/Makefile.rules'.  Stop.

Ditto for the "Simple" plugin.

[i00171 at rhino mcc16]$ cd ../Simple/


../../../../Makefile.common:61: ../../../../Makefile.config: No such 
file or directory
../../../../Makefile.common:69: /Makefile.rules: No such file or directory
make: *** No rule to make target `/Makefile.rules'.  Stop.
[i00171 at rhino Simple]$


I copied the "Simple" plugin to the configured directory

$ cd objs/tools/llvmc/plugins
$ cp -rf $LLVM_SRC/tools/llvmc/example/Simple MyPlugin

Changed the plugin name in the Makefile from "Simple" to
"MyPlugin", and
moved "Simple.td" to "MyPlugin.td"

$ make LLVMC_BUILTIN_PLUGINS=MyPlugin LLVMC_BASED_DRIVER_NAME=mydriver

That created "mydriver" executable for me.

- Sanjiv
> If you're building from some other dir, you'll need to update
> mcc16/Makefile, so it knows where Makefile.common is located.
>
>   
>> There are so many confusing things there: driver, plugins, example,
Skelton
>> etc.
>> The LLVMC-Tutorial doesn't clearly talk about them.
>>     
>
> Yes, I know, the documentation doesn't talk about creating standalone
> drivers. Sorry for that, I was planning to update it for ages...
> For now, please look at examples/Skeleton, which is a standalone
> driver skeleton, on which the mcc16 driver is based.
>
>   
>> I think the correct command line is
>> $ make LLVMC_BUILTIN_PLUGINS=MyPlugin LLVMC_BASED_DRIVER_NAME=mydriver
>>
>> rather than
>> $ make BUILTIN_PLUGINS=MyPlugin DRIVER_NAME=mydriver
>> (I found the later one in LLVMC-Reference)
>>     
>
> This section is about building the "main" llvmc driver and its
plugins.
> Creation of standalone drivers is not described in the docs yet (it
> was added relatively recently).
>
>

Hi Sanjiv,

2009/6/15 Sanjiv Gupta <sanjiv.gupta at
microchip.com>:
> I configure llvm into a separate directory from source.
> When I do the steps you mentioned in the source directory, this is what I
> get.
In that case, copy $LLVM_DIR/tools/llvmc/example/mcc16/Makefile to
$LLVM_OBJ_DIR/tools/llvmc/example/mcc16/Makefile and build from that
directory.

There is another way for building mcc16 in tree indepandent of sources

Change   DIRS = plugins driver 
to       DIRS = plugins driverexample/mcc16

in tools/llmc/Makefile works for me

mcc16 is then generated directly from the llvm main makefile.

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 behaviors?

Thanks,
Sanjiv

Mikhail Glushenkov wrote:
> Hi Sanjiv,
>
> 2009/6/15 Sanjiv Gupta <sanjiv.gupta at microchip.com>:
>   
>> I configure llvm into a separate directory from source.
>> When I do the steps you mentioned in the source directory, this is what
I
>> get.
>>     
>
> In that case, copy $LLVM_DIR/tools/llvmc/example/mcc16/Makefile to
> $LLVM_OBJ_DIR/tools/llvmc/example/mcc16/Makefile and build from that
> directory.
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>