# A Minimal Chisel Development Environment with Mill

The project is [here](https://github.com/ucb-bar/A-Minimal-Chisel-Project/tree/main), with instructions of setting everything up in the README file.&#x20;

So here, instead of reiterrating the set up flow, we will document some design choices of doing things.

### Scala build file

Mill will look for build files named as \`build.sc\`, \`build.mill\`, or \`build.mill.scala\`. We decided to use `build.mill.scala`as it makes it cleaner that a) this is a build file for mill, and b) this is a file with scala syntax. `build.mill`is another decent option, but unfortunately Github does not recognize this file extension name, and cannot properly do code highlighting.

### Source directory organization

For some reason, the build system cannot find the Elaborate.scala file if it is placed under `/src/main/scala/`. Instead, the current build system searches for source files under `<TopLevelObjectName>/src/main` and `<TopLevelObjectName>/src/main/scala`.

Therefore, we now have this a bit awkward `YourChiselProject` folder.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://tk233.gitbook.io/notes/risc-v-soc/a-minimal-chisel-development-environment-with-mill.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
