-
Notifications
You must be signed in to change notification settings - Fork 270
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
Make changes to building and packaging sairedis #1116
Make changes to building and packaging sairedis #1116
Conversation
This commit includes the following changes: 1. Use Debian build profiles instead of custom build targets to build different configurations of sairedis. Build profiles were designed for this purpose. This also makes the debian/rules file a bit cleaner. 2. Rely on the debug packages being automatically created, instead of us explicitly specifying it in debian/control. 3. Add actual support for excluding Python 2 binding build. 4. Make sure the compile flags used for building Python 2 and Python 3 are actually correct. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
62f6309
to
90c59f7
Compare
usr/lib/*/libsaimetadata.so | ||
usr/lib/*/libsaimeta.so |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should those be in non-dev package?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, these files are only needed at linking time, not during runtime. At linking time, the SONAME of these libraries (which, I believe, are libsaimetadata.so.0.0.0
and libsaimeta.so.0.0.0
for these two libraries) gets recorded in the binary/library, and that file instead gets loaded.
@saiarcot895 , sonic-swss-common validation break because debian/rules remove 'binary-syncd-vs' in this PR: https://github.com/sonic-net/sonic-swss-common/blob/master/.azure-pipelines/build-sairedis-template.yml dpkg-buildpackage: info: host architecture amd64 |
The build rules for sairedis have been simplified in sonic-net/sonic-sairedis#1116. As a result, build targets have changed. Update the build step here accordingly. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
…)" This may be causing or exposing some issues during tests. This reverts commit 7b39fc4.
* Make changes to building and packaging sairedis This commit includes the following changes: 1. Use Debian build profiles instead of custom build targets to build different configurations of sairedis. Build profiles were designed for this purpose. This also makes the debian/rules file a bit cleaner. 2. Rely on the debug packages being automatically created, instead of us explicitly specifying it in debian/control. 3. Add actual support for excluding Python 2 binding build. 4. Make sure the compile flags used for building Python 2 and Python 3 are actually correct. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Update pipeline file Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Fix argument for profile Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Exclude libsai package from the list of dependencies Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Allow multiple syslog artifacts during tests Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
…)" (sonic-net#1141) This may be causing or exposing some issues during tests. This reverts commit 7b39fc4.
* Make changes to building and packaging sairedis This commit includes the following changes: 1. Use Debian build profiles instead of custom build targets to build different configurations of sairedis. Build profiles were designed for this purpose. This also makes the debian/rules file a bit cleaner. 2. Rely on the debug packages being automatically created, instead of us explicitly specifying it in debian/control. 3. Add actual support for excluding Python 2 binding build. 4. Make sure the compile flags used for building Python 2 and Python 3 are actually correct. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Update pipeline file Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Fix argument for profile Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Exclude libsai package from the list of dependencies Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Allow multiple syslog artifacts during tests Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
* Make changes to building and packaging sairedis This commit includes the following changes: 1. Use Debian build profiles instead of custom build targets to build different configurations of sairedis. Build profiles were designed for this purpose. This also makes the debian/rules file a bit cleaner. 2. Rely on the debug packages being automatically created, instead of us explicitly specifying it in debian/control. 3. Add actual support for excluding Python 2 binding build. 4. Make sure the compile flags used for building Python 2 and Python 3 are actually correct. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Update pipeline file Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Fix argument for profile Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Exclude libsai package from the list of dependencies Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Allow multiple syslog artifacts during tests Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
…)" (sonic-net#1141) This may be causing or exposing some issues during tests. This reverts commit 7b39fc4.
…)' * Make changes to building and packaging sairedis This commit includes the following changes: 1. Use Debian build profiles instead of custom build targets to build different configurations of sairedis. Build profiles were designed for this purpose. This also makes the debian/rules file a bit cleaner. 2. Rely on the debug packages being automatically created, instead of us explicitly specifying it in debian/control. 3. Add actual support for excluding Python 2 binding during build. 4. Make sure the compile flags used for building Python 2 and Python 3 are actually correct. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Update pipeline file Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Fix argument for profile Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Exclude libsai package from the list of dependencies Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Allow multiple syslog artifacts during tests Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
* Reland 'Make changes to building and packaging sairedis (#1116)' * Make changes to building and packaging sairedis This commit includes the following changes: 1. Use Debian build profiles instead of custom build targets to build different configurations of sairedis. Build profiles were designed for this purpose. This also makes the debian/rules file a bit cleaner. 2. Rely on the debug packages being automatically created, instead of us explicitly specifying it in debian/control. 3. Add actual support for excluding Python 2 binding during build. 4. Make sure the compile flags used for building Python 2 and Python 3 are actually correct. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Update pipeline file Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Fix argument for profile Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Exclude libsai package from the list of dependencies Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Allow multiple syslog artifacts during tests Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Fix debug poackage name in dockerfile Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Fix armhf build due to python binary not existing Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> --------- Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
This PR makes the following changes:
different configurations of sairedis. Build profiles were designed for
this purpose. This also makes the debian/rules file a bit cleaner.
explicitly specifying it in debian/control.
are actually correct.