Tree-shake the lib linking list #4857

Closed
opened 2026-01-30 23:58:16 +00:00 by claunia · 1 comment
Owner

Originally created by @miniksa on GitHub (Nov 7, 2019).

Originally assigned to: @DHowett-MSFT on GitHub.

We should be able to get away with using umbrellas and not individual libs to link.

This represents shaking the tree to get rid of the duplication.

That is, I think we can get away with just using one of these:

  1. windowsapp.lib
  2. onecoreuap.lib
  3. onecoreuap_apiset.lib
  4. onecore.lib
  5. onecore_apiset.lib

and none of things like this:

  • kernel32.lib
  • gdi32.lib
  • user32.lib
    etc.

This represents someone groveling around common.build.post.props and friends and shaking them out.

Originally created by @miniksa on GitHub (Nov 7, 2019). Originally assigned to: @DHowett-MSFT on GitHub. We should be able to get away with using umbrellas and not individual libs to link. This represents shaking the tree to get rid of the duplication. That is, I think we can get away with just using one of these: 1. windowsapp.lib 2. onecoreuap.lib 3. onecoreuap_apiset.lib 4. onecore.lib 5. onecore_apiset.lib and none of things like this: - kernel32.lib - gdi32.lib - user32.lib etc. This represents someone groveling around `common.build.post.props` and friends and shaking them out.
Author
Owner

@DHowett-MSFT commented on GitHub (Nov 8, 2019):

This also solves our MinimalCoreWin problem.

@DHowett-MSFT commented on GitHub (Nov 8, 2019): This also solves our `MinimalCoreWin` problem.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4857