> For the complete documentation index, see [llms.txt](https://docs.eclipse.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eclipse.xyz/developers/tutorials-and-guides/developer-guides/dapp-deployment-tutorial-eclipse-devnet/creating-an-anchor-project-in-visual-studio-code/step-3-update-the-smart-contracts-cargo.toml-file.md).

# Step 3: Update the Smart Contract's Cargo.toml File

This step focuses on precisely configuring the `Cargo.toml` file for your smart contract, located in the `programs/nftminter` directory. Updating this file ensures your project has the correct dependencies and settings for compilation and deployment.

**Instructions**

1. **Open the Smart Contract's `Cargo.toml`**:
   * In Visual Studio Code, navigate to the `programs/nftminter` directory within your project.
   * Open the `Cargo.toml` file located in this directory.
2. **Update the File with the Following Configuration**:
   * Replace the existing content of the `Cargo.toml` file with the config below or your own:

     ```toml
     [package]
     name = "nft-minter"
     version = "0.1.0"
     description = "Created with Anchor"
     edition = "2021"

     [lib]
     crate-type = ["cdylib", "lib"]
     name = "nft_minter"

     [features]
     no-entrypoint = []
     no-idl = []
     no-log-ix-name = []
     cpi = ["no-entrypoint"]
     default = []

     [dependencies]
     anchor-lang = "0.29.0"
     anchor-spl = "0.29.0"
     ```
   * This configuration sets up your project with specific settings and dependencies:
     * **Package Information**: Names your project `nft-minter`, sets the version, and specifies it was created with Anchor.
     * **Library Settings**: Defines the type of Rust library being created and its name.
     * **Features**: Configures various Anchor features and compilation options.
     * **Dependencies**: Specifies the versions of `anchor-lang` and `anchor-spl` that your project depends on, ensuring compatibility with your Anchor framework version.
3. **Save Your Changes**:

   * After updating the `Cargo.toml` file, save it to apply the changes.

   <figure><img src="https://content.gitbook.com/content/syQqvSdLvlHIOsh2KCSe/blobs/WSYAkW46iESdmwyTUFlk/image.png" alt=""><figcaption><p>Loaded &#x26; Verified Dependencies</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eclipse.xyz/developers/tutorials-and-guides/developer-guides/dapp-deployment-tutorial-eclipse-devnet/creating-an-anchor-project-in-visual-studio-code/step-3-update-the-smart-contracts-cargo.toml-file.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.