Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unable to build Chapter 1

Open
  • Is something wrong?
#201 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust, wasm
Domain
build-system

Research direction

Reproduce the reported cargo build --release --target wasm32-unknown-unknown failure after adding the rltk dependency. Start by checking the project’s dependency declarations and the reported bracket-terminal 0.8.7 errors involving glow imports and InitHints; done means the Chapter 1 project builds successfully for the wasm target.

Written by the indexing model from the issue text.

Description

Hi,

after adding the rltk dependency I get the following error when I attempt to build the project:

cargo build --release --target wasm32-unknown-unknown
Compiling bracket-terminal v0.8.7
error[E0432]: unresolved imports glow::NativeFramebuffer, glow::NativeTexture
--> /home/occult/.cargo/registry/src/github.com-1ecc6299db9ec823/bracket-terminal-0.8.7/src/hal/gl_common/framebuffer.rs:3:24
|
3 | use glow::{HasContext, NativeFramebuffer, NativeTexture};
| ^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^ no NativeTexture in the root
| |
| no NativeFramebuffer in the root

error[E0609]: no field fitscreen on type hal::wasm::InitHints
--> /home/occult/.cargo/registry/src/github.com-1ecc6299db9ec823/bracket-terminal-0.8.7/src/initializer.rs:455:29
|
455 | self.platform_hints.fitscreen = fitscreen;
| ^^^^^^^^^ help: a field with a similar name exists: fullscreen

Some errors have detailed explanations: E0432, E0609.
For more information about an error, try rustc --explain E0432.

error: could not compile bracket-terminal due to 2 previous errors

Is this an issue with the bracket library wrapper?

Dominant language
Rust
Stars
967
Forks
166
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from amethyst/rustrogueliketutorial

All issues in amethyst/rustrogueliketutorial

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.