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

EmbeddedPkg: Enable build under VS2019 and fix build errors. #282

Merged
merged 1 commit into from
Jul 30, 2024

Conversation

apop5
Copy link
Contributor

@apop5 apop5 commented Jun 19, 2024

Description

Turn off modules in EmbeddedPkg's that cannot be compiled under VS.
Fix multiple 64 to 32 bit conversions.

8fa524e
6d66d4a (already included in #287)

  • Impacts functionality?
    • Functionality - Does the change ultimately impact how firmware functions?
    • Examples: Add a new library, publish a new PPI, update an algorithm, ...
  • Impacts security?
    • Security - Does the change have a direct security impact on an application,
      flow, or firmware?
    • Examples: Crypto algorithm change, buffer overflow fix, parameter
      validation improvement, ...
  • Breaking change?
    • Breaking change - Will anyone consuming this change experience a break
      in build or boot behavior?
    • Examples: Add a new library class, move a module to a different repo, call
      a function in a new library class in a pre-existing module, ...
  • Includes tests?
    • Tests - Does the change include any explicit test code?
    • Examples: Unit tests, integration tests, robot tests, ...
  • Includes documentation?
    • Documentation - Does the change contain explicit documentation additions
      outside direct code modifications (and comments)?
    • Examples: Update readme file, add feature readme file, link to documentation
      on an a separate Web page, ...

How This Was Tested

Local CI.

Integration Instructions

N/A

@VivianNK VivianNK requested a review from os-d July 16, 2024 17:59
EmbeddedPkg/EmbeddedPkg.dsc Outdated Show resolved Hide resolved
@apop5 apop5 force-pushed the personal/apop5/fixembeddedpkg branch from a293090 to 4c7b3ad Compare July 20, 2024 04:15
@github-actions github-actions bot added the impact:non-functional Does not have a functional impact label Jul 20, 2024
@apop5 apop5 force-pushed the personal/apop5/fixembeddedpkg branch from 4c7b3ad to 0b55e4f Compare July 23, 2024 22:48
@apop5 apop5 force-pushed the personal/apop5/fixembeddedpkg branch from 0b55e4f to 0402b56 Compare July 29, 2024 22:30
@apop5 apop5 merged commit c4264f3 into microsoft:release/202405 Jul 30, 2024
19 of 20 checks passed
apop5 added a commit to apop5/mu_tiano_plus that referenced this pull request Jan 6, 2025
…ft#282)

## Description

Turn off modules in EmbeddedPkg's that cannot be compiled under VS.
Fix multiple 64 to 32 bit conversions.


8fa524e
6d66d4a (already included in microsoft#287)

- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
    flow, or firmware?
  - Examples: Crypto algorithm change, buffer overflow fix, parameter
    validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
    in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
    a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
  - **Tests** - Does the change include any explicit test code?
  - Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
    outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
    on an a separate Web page, ...

## How This Was Tested
Local CI.

## Integration Instructions
N/A

Co-authored-by: Bret Barkelew <[email protected]>
apop5 added a commit that referenced this pull request Feb 4, 2025
## Description

Turn off modules in EmbeddedPkg's that cannot be compiled under VS.
Fix multiple 64 to 32 bit conversions.


8fa524e
6d66d4a (already included in #287)

- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
    flow, or firmware?
  - Examples: Crypto algorithm change, buffer overflow fix, parameter
    validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
    in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
    a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
  - **Tests** - Does the change include any explicit test code?
  - Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
    outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
    on an a separate Web page, ...

## How This Was Tested
Local CI.

## Integration Instructions
N/A

Co-authored-by: Bret Barkelew <[email protected]>
apop5 added a commit that referenced this pull request Feb 11, 2025
## Description

Turn off modules in EmbeddedPkg's that cannot be compiled under VS.
Fix multiple 64 to 32 bit conversions.


8fa524e
6d66d4a (already included in #287)

- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
    flow, or firmware?
  - Examples: Crypto algorithm change, buffer overflow fix, parameter
    validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
    in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
    a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
  - **Tests** - Does the change include any explicit test code?
  - Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
    outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
    on an a separate Web page, ...

## How This Was Tested
Local CI.

## Integration Instructions
N/A

Co-authored-by: Bret Barkelew <[email protected]>
apop5 added a commit that referenced this pull request Feb 14, 2025
## Description

Turn off modules in EmbeddedPkg's that cannot be compiled under VS.
Fix multiple 64 to 32 bit conversions.


8fa524e
6d66d4a (already included in #287)

- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
    flow, or firmware?
  - Examples: Crypto algorithm change, buffer overflow fix, parameter
    validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
    in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
    a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
  - **Tests** - Does the change include any explicit test code?
  - Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
    outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
    on an a separate Web page, ...

## How This Was Tested
Local CI.

## Integration Instructions
N/A

Co-authored-by: Bret Barkelew <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact:non-functional Does not have a functional impact
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants