an automated build including dependencies is needed for both verilator, ghdl, iverilog and cocotb. all of these are needed from source. specifically at the moment, verilator version v4.106 is needed. use "git checkout v4.106" to do this, after cloning.
Built Verilator successfully. Added Verilator dev-env-script. uri: https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=verilator-install;h=c136a0f75993bf65746a79b9f2ab2f78d15b1f4c;hb=HEAD Tell me about in which page to add in the Wiki.
(In reply to vklr@vkten.in from comment #1) > Built Verilator successfully. > > Added Verilator dev-env-script. fantastic! > Tell me about in which page to add in the Wiki. HDL_workflow page, in its own (new) subsection. even just "this is best installed with script <insert link>, we advise using only v4.106 at the moment"
Any payment can be had for this bug work and others to follow.
(In reply to vklr@vkten.in from comment #3) > Any payment can be had for this bug work and others to follow. yes of course. it needs to be 100% completed, and the task is for ghdl iverilog and cocotb as well.
Updated pages for Verilator. uri: https://libre-soc.org/HDL_workflow/ uri: https://libre-soc.org/HDL_workflow/verilator/ Please review.
I checked cocotb installation page. It's written that install neccessary prerequisites and then do pip install. Is it okay to do pip install?
Built GHDL successfully. Added Ghdl dev-env-script. uri: https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=ghdl-install;h=3de01a18a3d91c1e68b05516c586d74f8a8fafd3;hb=HEAD I have used GCC as backend. See this url: https://ghdl.readthedocs.io/en/latest/getting/index.html Please review.
(In reply to vklr@vkten.in from comment #7) > Built GHDL successfully. > > Added Ghdl dev-env-script. brilliant > > uri: > https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=ghdl-install; > h=3de01a18a3d91c1e68b05516c586d74f8a8fafd3;hb=HEAD > > I have used GCC as backend. > See this url: https://ghdl.readthedocs.io/en/latest/getting/index.html urr! that's horrible! i wasn't expecting that. ok i'll build it and check it, let you know. thanks veera. cocotb next, you'll need verilator and ghdl (they are dependencies)
Built Icarus Verilog successfully. Added iverilog dev-env-script. uri: https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=iverilog-install;h=0da8e4ab12c9c9bf1f159e6f56f7c9bf8a3baf7a;hb=HEAD Please review.
(In reply to Luke Kenneth Casson Leighton from comment #8) > (In reply to vklr@vkten.in from comment #7) > > Built GHDL successfully. > > > > Added Ghdl dev-env-script. > > > > > I have used GCC as backend. > > See this url: https://ghdl.readthedocs.io/en/latest/getting/index.html > > urr! that's horrible! i wasn't expecting that. ok i'll build it and > check it, let you know. > What's horrible: can you explain the particular thing. Want me to try mcode or llvm one.
(In reply to vklr@vkten.in from comment #10) > What's horrible: can you explain the particular thing. the fact that you have to use another compiler like that. quite fascinating. > Want me to try mcode or llvm one. nooo :) cocotb should in theory be straightforward https://docs.cocotb.org/en/stable/install.html get the list of dependencies from there, from the debian tab. git clone then "python3 setup.py install" this should be enough.
Built Cocotb successfully. Added cocotb dev-env-script. uri: https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=cocotb-install;h=4a34adbd1527a11ba2e8bbe25d84d34ad79e2777;hb=HEAD It's using python3 pip. This is the recommended way as per official install page. pip3 uses git to clone the repository and install. And it installs cocotb-bus dependency as well. We can specify the git tag or revision to pip3 for specific installation. cocotb-config --help and --version works. I have not run real simulation though, as I do not know how to do it. Can you check it. Or give me hints for how to do it. Please review.
(In reply to vklr@vkten.in from comment #12) > Built Cocotb successfully. > > Added cocotb dev-env-script. > > uri: > https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=cocotb-install; > h=4a34adbd1527a11ba2e8bbe25d84d34ad79e2777;hb=HEAD > > It's using python3 pip. i know. it's a damn nuisance. we don't need the hassle. please do "git pull". also, the compile needs to be in $SUDO_USER/src like the other scripts, i added a TODO note for you. > This is the recommended way as per official install > page. the "official" way can take a hike :) > pip3 uses git to clone the repository and install. And it installs cocotb-bus > dependency as well. yes. usually in a way that is also a damn nuisance, pulling in arbitrary untrusted untrustable dependencies that you have absolutely no control over, in a non-repeatable fashion. been here dozens of times. > We can specify the git tag or revision to pip3 for > specific > installation. > > cocotb-config --help and --version works. I have not run real simulation > though, > as I do not know how to do it. Can you check it. Or give me hints for how to > do > it. $ cd tests $ make it will be necessary to add "apt-get install python3-pytests" to the list of dependencies. the developers have failed to add that to the list of dependencies in setup.py. there's a way you're supposed to do that, for testing (python3 setup.py test) so you receive a notice. add python3-pytests to the list of build dependencies.
Updated the cocotb-install script. uri: https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=cocotb-install;h=67c7a572aca88c1448958e50c43bbeee46e5f0b7;hb=HEAD Please review.
(In reply to vklr@vkten.in from comment #14) > Updated the cocotb-install script. > > uri: > https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=cocotb-install; > h=67c7a572aca88c1448958e50c43bbeee46e5f0b7;hb=HEAD > > Please review. ok that seems to work - i didn't mean "remove python3-pip" however it does seem to work, including downloading cocotb_bus.
Updated ghdl-install script. uri: https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=ghdl-install;h=adcd752d65e538552e151c1f116e500575383c25;hb=HEAD Added --enable-default-pie option to gcc configure script. This option should match system gcc setting. Otherwise during ghdl called linker stage error occurs about non fpic and fpic code mismatch.
(In reply to Luke Kenneth Casson Leighton from comment #15) > (In reply to vklr@vkten.in from comment #14) > > Updated the cocotb-install script. > > > > uri: > > https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=cocotb-install; > > h=67c7a572aca88c1448958e50c43bbeee46e5f0b7;hb=HEAD > > > > Please review. > > ok that seems to work - i didn't mean "remove python3-pip" however > it does seem to work, including downloading cocotb_bus. Install works without python3-pip, checked using fresh install. Ran make tests with alteast one test passing each with verilator, ghdl and iverilog. I had to rebuild ghdl fpic mismatch, see previous post. Do you want me to add python3-pip for some reason.
no if it has succeeded including finding and installing cocotb_bus then it should be good. you can check with ls /usr/local/lib/python3.7/dist-packages cocotb_bus egg should be there
Updated pages for GHDL. uri: https://libre-soc.org/HDL_workflow/ uri: https://libre-soc.org/HDL_workflow/ghdl/ Please review.
Updated pages for Icarus Verilog. uri: https://libre-soc.org/HDL_workflow/ uri: https://libre-soc.org/HDL_workflow/iverilog/ Please review.
Updated pages for Cocotb. uri: https://libre-soc.org/HDL_workflow/ uri: https://libre-soc.org/HDL_workflow/cocotb/ Please review.
luke: toml local dates have to be of the form 2021-01-23, you can't use 2021jan23. https://toml.io/en/v1.0.0#local-date toml follows https://tools.ietf.org/html/rfc3339
(In reply to Jacob Lifshay from comment #22) > luke: toml local dates have to be of the form 2021-01-23, you can't use > 2021jan23. > https://toml.io/en/v1.0.0#local-date > toml follows https://tools.ietf.org/html/rfc3339 thx, i couldn't remember, was going to sort it out when the error occurred by running budgetsync