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

bugzilla-daemon at libre-riscv.org bugzilla-daemon at libre-riscv.org
Tue Mar 10 04:28:10 GMT 2020


--- Comment #189 from Yehowshua <yimmanuel3 at gatech.edu> ---
> By “full potential” I mean visual debugging and inspection. I am using Pycharm, but > this applies to any fairly advanced IDE, like Eclipse/PyDev. They usually rely on ‘native’ (/usr/bin/) or virtual (provided by virtualenv, conda et c.) Python prefixes > for code inspection, and chroot is neither of them.

@Jock Tanner,

Do you think binding a container to a repo on host would solve your pyCharm
You would have pyCharm on host...

You can also have a python REPL in your Container, and the connect to that
Python instance over a port the docker container exposes...

I've seen that done before.


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

More information about the libre-riscv-dev mailing list