[libre-riscv-dev] [Bug 178] first coriolis2 tutorial, workflow and "test project" page

[bugzilla-daemon at libre-riscv.org]

http://bugs.libre-riscv.org/show_bug.cgi?id=178

--- Comment #201 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to Jock Tanner from comment #200)

> Well, if “no extra software” is the main concern, then I guess my initial
> idea of installing Pycharm locally in chroot will do just fine. It's
> completely self-contained and requires no modification to the system, with
> the exception of:
> 
> - setup folder (can be installed in home folder, no root required),
> - global settings folder (also in home folder),
> - project settings folder (can be put in '.git/info/exclude' or
> '.gitignore', which I usually do).
> 
> Delete that 3 objects, and you'll never remember that you used it.
> 
> Actually, I've tried it already, and all went well 

excellent

> with one exception: I can't get binary extensions indexed. 

this does not surprise me at all.  and you won't find anything anyway:
there are zero docstrings 

> Yes, I'd like to walk through Hurricane
> attributes in editor. =) I think it's worth a little investigation.

you will likely need the coriolisEnv.py settings. i believe pycharm
actually *executes* the module (imports it, which can have side-effects).

clearly, to execute the Hurricane.so that involves being able to load
the dynamic libraries it's linked to.

that in turn involves having coriolisEnv.py environment variables set up

it also implies having access to the entire coriolis binaries and libraries.

anyway - focus.

let me know how you get on with the analogy of creating something similar to
ioring.py, to create "Pads" that you can see in the experiments5 and alu_hier
nmigen benchs.  you might even be able to use the code *from* coriolis2 that
imports ioring.py as a base.

-- 
You are receiving this mail because:
You are on the CC list for the bug.