Skip to content

Update .vscode and .devcontainer files#6246

Merged
serprex merged 8 commits intoHarbourMasters:developfrom
coavins:vscode
Feb 26, 2026
Merged

Update .vscode and .devcontainer files#6246
serprex merged 8 commits intoHarbourMasters:developfrom
coavins:vscode

Conversation

@coavins
Copy link
Copy Markdown
Contributor

@coavins coavins commented Feb 9, 2026

This pr does two things:

  • Update the outdated Dockerfile. It now uses Ubuntu 24 LTS instead of 22, and installs all of the missing dependencies.
  • Update tasks.json to include the Linux steps from BUILDING.md. I kept the existing Windows steps, vscode will automatically select the commands appropriate for your os.

The project builds just fine for me without the container, but the container is useful because I don't have easy access to clang-format-14.

Build Artifacts

@Malkierian
Copy link
Copy Markdown
Contributor

I believe we still had it based on 22 for a reason.

@coavins
Copy link
Copy Markdown
Contributor Author

coavins commented Feb 9, 2026

If I use the container as defined in master, I'm unable to build the project. I assume ubuntu 22 ships a version of cmake that is too old.

CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
  CMake 3.26.0 or higher is required.  You are running version 3.22.1

I can remove the changes to the container from this PR if you want to deal with that separately.

@Malkierian
Copy link
Copy Markdown
Contributor

There should be a way of updating the cmake version that gets installed in the docker, because our github workflows use 22 as well and don't have any issues with it.

This commit makes some changes to the dockerfile to make it work again.
We install cmake from source in order to meet the minimum required
version specified in the CMakeLists.txt file. We build the same version
that is installed on the CI runner image.

We also build tinyxml2 from source because we need some cmake files
that are apparently not included in the apt package.
@coavins
Copy link
Copy Markdown
Contributor Author

coavins commented Feb 9, 2026

I switched it back to ubuntu 22. I added some steps to build cmake from source so we can use the same version that's on the CI runners: https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md

@Malkierian
Copy link
Copy Markdown
Contributor

Cool. I don't have any inherent problems with the current state of this now, but I have no way of testing anything in it. What uses tasks.json anyway?

@serprex serprex requested a review from Malkierian February 9, 2026 23:37
@ShishuTheDragon
Copy link
Copy Markdown
Contributor

See also #6211

What uses tasks.json anyway?

  • It tells VS Code what to do when you press Ctrl+Shift+B.
  • If you’ve also set up the debugger, it tells VS Code how to build prior to launching the Ship process.

@coavins
Copy link
Copy Markdown
Contributor Author

coavins commented Feb 13, 2026

I merged the changes from #6211. The tasks work for me on linux, I can't test other platforms.

Copy link
Copy Markdown
Contributor

@Malkierian Malkierian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would assume, since it's a VS Code thing, if they work on one platform, they'll work on any that you use VS Code on.

@coavins
Copy link
Copy Markdown
Contributor Author

coavins commented Feb 15, 2026

Whoops... wrong branch

Comment thread .vscode/tasks.json Outdated
@serprex
Copy link
Copy Markdown
Member

serprex commented Feb 24, 2026

why LUS bump?

@Malkierian
Copy link
Copy Markdown
Contributor

I am extremely surprised the one just merged created no conflicts with this one.

@serprex serprex merged commit c2cf154 into HarbourMasters:develop Feb 26, 2026
6 checks passed
@serprex
Copy link
Copy Markdown
Member

serprex commented Feb 26, 2026

ugh #6211 was pointed at develop-copper

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants