Publish chisel3.std

[ZenithalHourlyRate]

Contributor Checklist

• Did you add Scaladoc to every public function/method?
• Did you add at least one test demonstrating the PR?
• Did you delete any extraneous printlns/debugging code?
• Did you specify the type of improvement?
• Did you add appropriate documentation in docs/src?
• Did you state the API impact?
• Did you specify the code generation impact?
• Did you request a desired merge strategy?
• Did you add text to be included in the Release Notes for this change?

Type of Improvement

bug fix

chisel3.std was not published, and downstream users want to use this, e.g. rocket-chip.

API Impact

Publish chisel3.std

Backend Code Generation Impact

Desired Merge Strategy

Squash

Release Notes

Publish chisel3.std

Reviewer Checklist (only modified by reviewer)

• Did you add the appropriate labels?
• Did you mark the proper milestone (Bug fix: 3.4.x, [small] API extension: 3.5.x, API modification or big change: 3.6.0)?
• Did you review?
• Did you check whether all relevant Contributor checkboxes have been checked?
• Did you do one of the following when ready to merge:
  • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
  • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

[sequencer]

Nice catch. I was always compiling from source, and never detected this before.

[jackkoenig]

This does not correctly publish stdlib.

1. You need to set the name key of this project or this just clobbers the normal chisel3 publishing (it thinks it is the project named chisel3 and thus publishes to the exact same artifact name as chisel3).
2. It is not included when running +publishLocal, please figure out how to make it publish the standard way, you currently have to run standardLibrary / publishLocal to get it to publish.

[ZenithalHourlyRate]

standardLibrary depending on chisel is troublesome (more specifically, it uses chisel3.util) and could result in cyclic dependency if we want to publish it to stardardLibrary in chisel by a single +publish (aggregate standardLibrary)

There are three ways to resolve the issue

1. Create a chisel3-util package and make standardLibrary depending on this, like this commit. However, chisel package is not the root package anymore and we need sbt chisel/xxx, which is unacceptable.
2. Move the current src into util/src or some other path and then the (virtual) chisel package is the root package. This is a big change in directory structure.
3. Publish chisel3-std as a standalone package

[ZenithalHourlyRate]

The easier way to resolve the issue is to move stdlib/src into src.

[ZenithalHourlyRate]

Since caf0518 we can remove the CI check on standardLibrary/test

[sequencer]

I think split the stdlib to chisel-stdlib is good choice, since we never released which(only those build from source(like me))