-
Notifications
You must be signed in to change notification settings - Fork 88
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
Update lib target soversion #2267
Conversation
Why are we dropping the patch version? |
|
Codecov Report
@@ Coverage Diff @@
## develop #2267 +/- ##
===========================================
+ Coverage 91.37% 91.46% +0.09%
===========================================
Files 439 433 -6
Lines 16493 16174 -319
===========================================
- Hits 15069 14792 -277
+ Misses 1424 1382 -42 |
This build is OK for merge ✅ |
🔴bert_base_cased_fp16: FAILED: MIGraphX is not within tolerance - check verbose output🔴bert_large_uncased_fp16: FAILED: MIGraphX is not within tolerance - check verbose output🔴distilgpt2_fp16: FAILED: MIGraphX is not within tolerance - check verbose output |
The major, minor and patch should be part of the SO major version: math(EXPR MIGRAPHX_SO_MAJOR_VERSION "(${PROJECT_VERSION_MAJOR} * 1000 * 1000) + (${PROJECT_VERSION_MINOR} * 1000) + ${PROJECT_VERSION_PATCH}")
set(MIGRAPHX_SO_VERSION ${MIGRAPHX_SO_MAJOR_VERSION}.0) Or we if we can drop the minor version it could just be: math(EXPR MIGRAPHX_SO_VERSION "(${PROJECT_VERSION_MAJOR} * 1000 * 1000) + (${PROJECT_VERSION_MINOR} * 1000) + ${PROJECT_VERSION_PATCH}") |
I don't see any difference between the two EXPRs that you mentioned. |
One has the version as |
Are we good to approve this change? Or need further changes here? All other modules are using same format for lib version |
Merge conflict and you have not addressed Pauls comments |
The convention for actual library files that we have in ROCm across all the component is to have major.minor.{encoded ROCm version}. |
Summary of proposed changes: