Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

6.x - Initial GCC toolset implementation #1931

Draft
wants to merge 1 commit into
base: 6.x
Choose a base branch
from

Conversation

nickclark2016
Copy link
Member

What does this PR do?

Adds a toolset abstraction and implementation for GCC.

How does this PR change Premake's behavior?

No outwards facing behavioral changes.

Anything else we should know?

Each toolset will need to be registered in order to be used by the "toolset" API.

Did you check all the boxes?

  • Focus on a single fix or feature; remove any unrelated formatting or code changes
  • Add unit tests showing fix or feature works; all tests pass
  • Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
  • Follow our coding conventions
  • Minimize the number of commits
  • Align documentation to your changes

You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!

@nickclark2016 nickclark2016 changed the title Initial GCC toolset implementation 6.x - Initial GCC toolset implementation Aug 21, 2022
-- user can specify in a script. Each individual toolset defines the architectures that it is
-- valid for and mappings for turning premake fields into tool-specific outputs.
--
-- C++ toolsets must define the following functions on the toolset object:
Copy link
Contributor

Choose a reason for hiding this comment

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

Should name tools be there too?
gcc/g++/ld/ar/rc

Copy link
Member Author

Choose a reason for hiding this comment

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

Good call. It should provide the tool executable names as well.

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.

2 participants