Skip to content

Conversation

@PeteDavidson
Copy link

Uses bitbake -c update_crates xxxx instead of the depricated cargo-bitbake. This command creates the xxxx-crates.inc file. This command is done just once to creaet the file which is then must be commited to the meta-iotedge repo.

New file structure:

aziot-edged
aziot-edged-1.5.24.bb All normal bb stuff
aziot-crates.inc Crates info generated by update_crates
iot-identity-service.inc IoT Identity Service refs
files
*.patch
aziot-edged.service
iotedge.conf

Uses bitbake -c update_crates xxxx instead of the depricated
cargo-bitbake. This command creates the xxxx-crates.inc file.
This command is done just once to creaet the file which is
then must be  commited to the meta-iotedge repo.

New file structure:

aziot-edged
  aziot-edged-1.5.24.bb     All normal bb stuff
  aziot-crates.inc          Crates info generated by update_crates
  iot-identity-service.inc  IoT Identity Service refs
  files
    *.patch
    aziot-edged.service
    iotedge.conf
@PeteDavidson
Copy link
Author

@microsoft-github-policy-service agree company="Lexmark"

@Lexmark-chad
Copy link

Is anyone from Microsoft monitoring PR's? Also, I'm not sure what meta-iotedge checkinExpected — Waiting for status to be reported represents. Anything we need to do to get this to move forward? Thnx.

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