ml-explore / ml-explore/mlx-data

Is MLX_ENABLE_AWS environment variable required?

Open
#113 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
483
Forks
62
PR merge metrics
No merged PRs in 30d

Description

Hello MLX Team,

I noticed that the MLX_ENABLE_AWS environment variable is currently specified when building mlx-data in .circleci/config.yml:

https://github.com/ml-explore/mlx-data/blob/2f431e90a06c33d2e3f78019b32c563e8fd8a71a/.circleci/config.yml#L47-L49

https://github.com/ml-explore/mlx-data/blob/2f431e90a06c33d2e3f78019b32c563e8fd8a71a/.circleci/config.yml#L115-L116

https://github.com/ml-explore/mlx-data/blob/2f431e90a06c33d2e3f78019b32c563e8fd8a71a/.circleci/config.yml#L149-L150

However, I encountered the following message during the build process:

  -- Configuring done (8.7s)
  -- Generating done (0.1s)
  CMake Warning:
    Manually-specified variables were not used by the project:
      MLX_ENABLE_AWS

Based on my testing, the build remains unaffected even without this environment variable. Given this, would it be better to remove it?

Contributor guide

Open the contributing guide

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.

Research direction

Start by inspecting the three MLX_ENABLE_AWS entries in .circleci/config.yml and checking whether the variable is referenced by the project's CMake configuration. Compare builds with and without it, then confirm the warning and build behavior before deciding whether all three entries can be removed.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, cpp
Domain
build-system, ci-cd
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.