Skip to content

Fix #24130 by adding an empty dependency group to the code that generates Microsoft.ML.OnnxRuntime.nuspec - #24131

Merged
snnn merged 1 commit into
microsoft:mainfrom
benjamin-hodgson:native_tfm
Apr 23, 2025
Merged

Fix #24130 by adding an empty dependency group to the code that generates Microsoft.ML.OnnxRuntime.nuspec#24131
snnn merged 1 commit into
microsoft:mainfrom
benjamin-hodgson:native_tfm

Conversation

@benjamin-hodgson

@benjamin-hodgson benjamin-hodgson commented Mar 21, 2025

Copy link
Copy Markdown
Contributor

Description

As detailed in the issue (#24130), the Microsoft.ML.OnnxRuntime nuspec needs an additional dependency group for the native TFM, to allow it to be referenced via PackageReference in vcxproj projects.

I took a peek at the code after filing the issue, since it seemed like it ought to be a simple fix. It looks like the nuspec file for the Microsoft.ML.OnnxRuntime package is generated by the python code in generate_nuspec_for_native_nuget.py, so I just added a line of code there.

However I'm not sure how the build system invokes this generator so I haven't been able to test it in situ. Let me know if this isn't the right fix!

Motivation and Context

See detailed description in #24130

@benjamin-hodgson benjamin-hodgson changed the title Fix #24130 by adding an empty dependency group Fix #24130 by adding an empty dependency group to the code that generates Microsoft.ML.OnnxRuntime.nuspec Mar 21, 2025
@snnn

snnn commented Mar 21, 2025

Copy link
Copy Markdown
Contributor

/azp run Big Models, Linux Android Emulator QNN CI Pipeline, Linux CPU CI Pipeline, Linux CPU Minimal Build E2E CI Pipeline, Linux GPU CI Pipeline, Linux GPU TensorRT CI Pipeline

@snnn

snnn commented Mar 21, 2025

Copy link
Copy Markdown
Contributor

/azp run Linux OpenVINO CI Pipeline, Linux QNN CI Pipeline, ONNX Runtime Web CI Pipeline, onnxruntime-binary-size-checks-ci-pipeline, Win_TRT_Minimal_CUDA_Test_CI, Windows ARM64 QNN CI Pipeline, Windows GPU Doc Gen CI Pipeline, Windows x64 QNN CI Pipeline

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 6 pipeline(s).

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 8 pipeline(s).

@benjamin-hodgson

Copy link
Copy Markdown
Contributor Author

I think this is ready to merge.

@benjamin-hodgson

benjamin-hodgson commented Apr 21, 2025

Copy link
Copy Markdown
Contributor Author

@snnn Can we get this PR merged please? I'd really like it to get in to the next release, when that happens. Thanks!

@snnn

snnn commented Apr 21, 2025

Copy link
Copy Markdown
Contributor

Sorry I was OOF last week. Brought my kids for a family trip.

@snnn snnn closed this Apr 21, 2025
@snnn snnn reopened this Apr 21, 2025
@benjamin-hodgson

Copy link
Copy Markdown
Contributor Author

No worries, I was off for spring break with my 1-year-old too :)

@snnn
snnn merged commit d1ac97e into microsoft:main Apr 23, 2025
@benjamin-hodgson
benjamin-hodgson deleted the native_tfm branch April 23, 2025 12:20
intbf pushed a commit to intbf/onnxruntime that referenced this pull request Apr 25, 2025
…hat generates Microsoft.ML.OnnxRuntime.nuspec (microsoft#24131)

### Description
As detailed in the issue (microsoft#24130), the Microsoft.ML.OnnxRuntime nuspec
needs an additional dependency group for the `native` TFM, to allow it
to be referenced via `PackageReference` in vcxproj projects.

I took a peek at the code after filing the issue, since it seemed like
it ought to be a simple fix. It looks like the nuspec file for the
`Microsoft.ML.OnnxRuntime` package is generated by the python code in
`generate_nuspec_for_native_nuget.py`, so I just added a line of code
there.

However I'm not sure how the build system invokes this generator so I
haven't been able to test it in situ. Let me know if this isn't the
right fix!

### Motivation and Context

See detailed description in microsoft#24130

Signed-off-by: bfilipek <bartlomiej.filipek@intel.com>
@benjamin-hodgson

Copy link
Copy Markdown
Contributor Author

Do you have a rough idea when I should expect this fix to make it to a RTM version of the package? Looks like it didn't make it into the rel-1.22.0 branch.

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