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

Symbol export with llvm-ml

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cmake
Domain
build-system

Research direction

Review the attached cmake.patch and fcontext.patch first, focusing on the llvm-ml command options and symbol-export handling described in the issue. Reproduce compilation of boost.context with clang-cl and llvm-ml, then verify that 64-bit builds succeed without breaking existing functionality.

Written by the indexing model from the issue text.

Description

Hi all,

I thought I'd share 2 patches that I needed to successfully compile boost.context on clang-cl with llvm-ml. I think these can't exactly be applied as-is without breaking existing functionality, but it basically stems down to /quiet not being supported, and needing to pass --m64 to enable 64-bit aka the mt64.exe equivalent. The other thing is how symbols get exported, the PROC call doesn't support EXPORT however __declspec(dllexport) on the C signature does work.

cmake.patch

fcontext.patch

Kind regards

Dominant language
Assembly
Stars
371
Forks
186
Avg merge
4d 13h
Merged PRs (30d)
1

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 boostorg/context

All issues in boostorg/context

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.