Public analysis content #142
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Start to correct errors caused by this change.
With it build fails. This is a known problem solved in PySide6. See https://bugreports.qt.io/browse/PYSIDE-1699
This will allow to develop API using internals of lima data, such as python bindings. For this use case, depending on dumpers and handlers is too much hurdle.
kleag
added a commit
that referenced
this pull request
Jul 29, 2022
* Update README.md * Update README.md * Update README.md * Public analysis content (#142) * Bump cmake version to the one from Ubuntu 20.04 * Errors on deprecated features removed from Qt6 Start to correct errors caused by this change. * Activate manylinux with qt6 image build * Correct typo * Correct Qt configure * Correct Qt configure command * Qt6 build use Ninja * Build llvm on actions * Try push to docker hub * New try * Remove useless job * Build llvm again * Compile more LLVM projects * Correct typo * Correct llvm projects list * Remove unknown llvm project * Add gcc build * LLVM build uses recent GCC * Activate llvm build action * Add missing ARG * Correct gcc setting in llvm build * Use for real recent gcc to build llvm * Disable build llvm-libc as it fails with gcc * Switch to building qt6 * Remove useless env var * Compile qt with gcc * Correct parent image name * Correct gcc path * Add missing login to docker hub * Use strings for version numbers in env vars. This avoids to accidentally change "3.10" in "3.1". * Build PySide * Add message * Correct variable name * Add Qt path to pyside setup command * Add missing gcc version arg * Forgot to copy gcc into container * Correct docker image name * Change Qt version * Retrieve LLVM in Qt and PySide image * Remove spurious diff trace * Remove traces of hard coded Qt5 in cmake files * Update workflow * Should correct pyside build Force also the use of python limited api to be able to generate abi3 wheels. * Do not build qt. It was successful * Move setup of clang before its use * From with args must be an as in the beginning * Correction * Try to avoid no space left on device in action * Free diskspace on github actions * Try again llvm with clang only * Simplify dockerfile * Do not need gcc * Correct typo * Add missing package in image * Switch back to Qt5 and python 3.7 * Add missing package * Add all previous packages * Change * Switch to c++17 for qt15 * Copy again gcc in the image * Qt 5.12 uses make instead of cmake * Correct a path * Switch to clang * Correct pyside2 build * Remove pyside6 option * Try another thing * ... * Remove standalone option With it build fails. This is a known problem solved in PySide6. See https://bugreports.qt.io/browse/PYSIDE-1699 * Client returns AnalysisContent This will allow to develop API using internals of lima data, such as python bindings. For this use case, depending on dumpers and handlers is too much hurdle. * Build public_analysis_content branch in actions * New github action * Do not build pyside image * Remove llvm * Must build with PySide * Correct python version * Pass the branch to the docker build command * Correct typo * Switch to manylinux_2_28 * Works locally
kleag
added a commit
that referenced
this pull request
Jul 29, 2022
* Update README.md * Update README.md * Update README.md * Public analysis content (#142) * Bump cmake version to the one from Ubuntu 20.04 * Errors on deprecated features removed from Qt6 Start to correct errors caused by this change. * Activate manylinux with qt6 image build * Correct typo * Correct Qt configure * Correct Qt configure command * Qt6 build use Ninja * Build llvm on actions * Try push to docker hub * New try * Remove useless job * Build llvm again * Compile more LLVM projects * Correct typo * Correct llvm projects list * Remove unknown llvm project * Add gcc build * LLVM build uses recent GCC * Activate llvm build action * Add missing ARG * Correct gcc setting in llvm build * Use for real recent gcc to build llvm * Disable build llvm-libc as it fails with gcc * Switch to building qt6 * Remove useless env var * Compile qt with gcc * Correct parent image name * Correct gcc path * Add missing login to docker hub * Use strings for version numbers in env vars. This avoids to accidentally change "3.10" in "3.1". * Build PySide * Add message * Correct variable name * Add Qt path to pyside setup command * Add missing gcc version arg * Forgot to copy gcc into container * Correct docker image name * Change Qt version * Retrieve LLVM in Qt and PySide image * Remove spurious diff trace * Remove traces of hard coded Qt5 in cmake files * Update workflow * Should correct pyside build Force also the use of python limited api to be able to generate abi3 wheels. * Do not build qt. It was successful * Move setup of clang before its use * From with args must be an as in the beginning * Correction * Try to avoid no space left on device in action * Free diskspace on github actions * Try again llvm with clang only * Simplify dockerfile * Do not need gcc * Correct typo * Add missing package in image * Switch back to Qt5 and python 3.7 * Add missing package * Add all previous packages * Change * Switch to c++17 for qt15 * Copy again gcc in the image * Qt 5.12 uses make instead of cmake * Correct a path * Switch to clang * Correct pyside2 build * Remove pyside6 option * Try another thing * ... * Remove standalone option With it build fails. This is a known problem solved in PySide6. See https://bugreports.qt.io/browse/PYSIDE-1699 * Client returns AnalysisContent This will allow to develop API using internals of lima data, such as python bindings. For this use case, depending on dumpers and handlers is too much hurdle. * Build public_analysis_content branch in actions * New github action * Do not build pyside image * Remove llvm * Must build with PySide * Correct python version * Pass the branch to the docker build command * Correct typo * Switch to manylinux_2_28 * Works locally
Deurstann
pushed a commit
that referenced
this pull request
Aug 1, 2022
* Bump cmake version to the one from Ubuntu 20.04 * Errors on deprecated features removed from Qt6 Start to correct errors caused by this change. * Activate manylinux with qt6 image build * Correct typo * Correct Qt configure * Correct Qt configure command * Qt6 build use Ninja * Build llvm on actions * Try push to docker hub * New try * Remove useless job * Build llvm again * Compile more LLVM projects * Correct typo * Correct llvm projects list * Remove unknown llvm project * Add gcc build * LLVM build uses recent GCC * Activate llvm build action * Add missing ARG * Correct gcc setting in llvm build * Use for real recent gcc to build llvm * Disable build llvm-libc as it fails with gcc * Switch to building qt6 * Remove useless env var * Compile qt with gcc * Correct parent image name * Correct gcc path * Add missing login to docker hub * Use strings for version numbers in env vars. This avoids to accidentally change "3.10" in "3.1". * Build PySide * Add message * Correct variable name * Add Qt path to pyside setup command * Add missing gcc version arg * Forgot to copy gcc into container * Correct docker image name * Change Qt version * Retrieve LLVM in Qt and PySide image * Remove spurious diff trace * Remove traces of hard coded Qt5 in cmake files * Update workflow * Should correct pyside build Force also the use of python limited api to be able to generate abi3 wheels. * Do not build qt. It was successful * Move setup of clang before its use * From with args must be an as in the beginning * Correction * Try to avoid no space left on device in action * Free diskspace on github actions * Try again llvm with clang only * Simplify dockerfile * Do not need gcc * Correct typo * Add missing package in image * Switch back to Qt5 and python 3.7 * Add missing package * Add all previous packages * Change * Switch to c++17 for qt15 * Copy again gcc in the image * Qt 5.12 uses make instead of cmake * Correct a path * Switch to clang * Correct pyside2 build * Remove pyside6 option * Try another thing * ... * Remove standalone option With it build fails. This is a known problem solved in PySide6. See https://bugreports.qt.io/browse/PYSIDE-1699 * Client returns AnalysisContent This will allow to develop API using internals of lima data, such as python bindings. For this use case, depending on dumpers and handlers is too much hurdle. * Build public_analysis_content branch in actions * New github action * Do not build pyside image * Remove llvm * Must build with PySide * Correct python version * Pass the branch to the docker build command * Correct typo * Switch to manylinux_2_28 * Works locally
Deurstann
pushed a commit
that referenced
this pull request
Aug 1, 2022
* Update README.md * Update README.md * Update README.md * Public analysis content (#142) * Bump cmake version to the one from Ubuntu 20.04 * Errors on deprecated features removed from Qt6 Start to correct errors caused by this change. * Activate manylinux with qt6 image build * Correct typo * Correct Qt configure * Correct Qt configure command * Qt6 build use Ninja * Build llvm on actions * Try push to docker hub * New try * Remove useless job * Build llvm again * Compile more LLVM projects * Correct typo * Correct llvm projects list * Remove unknown llvm project * Add gcc build * LLVM build uses recent GCC * Activate llvm build action * Add missing ARG * Correct gcc setting in llvm build * Use for real recent gcc to build llvm * Disable build llvm-libc as it fails with gcc * Switch to building qt6 * Remove useless env var * Compile qt with gcc * Correct parent image name * Correct gcc path * Add missing login to docker hub * Use strings for version numbers in env vars. This avoids to accidentally change "3.10" in "3.1". * Build PySide * Add message * Correct variable name * Add Qt path to pyside setup command * Add missing gcc version arg * Forgot to copy gcc into container * Correct docker image name * Change Qt version * Retrieve LLVM in Qt and PySide image * Remove spurious diff trace * Remove traces of hard coded Qt5 in cmake files * Update workflow * Should correct pyside build Force also the use of python limited api to be able to generate abi3 wheels. * Do not build qt. It was successful * Move setup of clang before its use * From with args must be an as in the beginning * Correction * Try to avoid no space left on device in action * Free diskspace on github actions * Try again llvm with clang only * Simplify dockerfile * Do not need gcc * Correct typo * Add missing package in image * Switch back to Qt5 and python 3.7 * Add missing package * Add all previous packages * Change * Switch to c++17 for qt15 * Copy again gcc in the image * Qt 5.12 uses make instead of cmake * Correct a path * Switch to clang * Correct pyside2 build * Remove pyside6 option * Try another thing * ... * Remove standalone option With it build fails. This is a known problem solved in PySide6. See https://bugreports.qt.io/browse/PYSIDE-1699 * Client returns AnalysisContent This will allow to develop API using internals of lima data, such as python bindings. For this use case, depending on dumpers and handlers is too much hurdle. * Build public_analysis_content branch in actions * New github action * Do not build pyside image * Remove llvm * Must build with PySide * Correct python version * Pass the branch to the docker build command * Correct typo * Switch to manylinux_2_28 * Works locally
Deurstann
pushed a commit
that referenced
this pull request
Aug 1, 2022
* Update README.md * Update README.md * Update README.md * Public analysis content (#142) * Bump cmake version to the one from Ubuntu 20.04 * Errors on deprecated features removed from Qt6 Start to correct errors caused by this change. * Activate manylinux with qt6 image build * Correct typo * Correct Qt configure * Correct Qt configure command * Qt6 build use Ninja * Build llvm on actions * Try push to docker hub * New try * Remove useless job * Build llvm again * Compile more LLVM projects * Correct typo * Correct llvm projects list * Remove unknown llvm project * Add gcc build * LLVM build uses recent GCC * Activate llvm build action * Add missing ARG * Correct gcc setting in llvm build * Use for real recent gcc to build llvm * Disable build llvm-libc as it fails with gcc * Switch to building qt6 * Remove useless env var * Compile qt with gcc * Correct parent image name * Correct gcc path * Add missing login to docker hub * Use strings for version numbers in env vars. This avoids to accidentally change "3.10" in "3.1". * Build PySide * Add message * Correct variable name * Add Qt path to pyside setup command * Add missing gcc version arg * Forgot to copy gcc into container * Correct docker image name * Change Qt version * Retrieve LLVM in Qt and PySide image * Remove spurious diff trace * Remove traces of hard coded Qt5 in cmake files * Update workflow * Should correct pyside build Force also the use of python limited api to be able to generate abi3 wheels. * Do not build qt. It was successful * Move setup of clang before its use * From with args must be an as in the beginning * Correction * Try to avoid no space left on device in action * Free diskspace on github actions * Try again llvm with clang only * Simplify dockerfile * Do not need gcc * Correct typo * Add missing package in image * Switch back to Qt5 and python 3.7 * Add missing package * Add all previous packages * Change * Switch to c++17 for qt15 * Copy again gcc in the image * Qt 5.12 uses make instead of cmake * Correct a path * Switch to clang * Correct pyside2 build * Remove pyside6 option * Try another thing * ... * Remove standalone option With it build fails. This is a known problem solved in PySide6. See https://bugreports.qt.io/browse/PYSIDE-1699 * Client returns AnalysisContent This will allow to develop API using internals of lima data, such as python bindings. For this use case, depending on dumpers and handlers is too much hurdle. * Build public_analysis_content branch in actions * New github action * Do not build pyside image * Remove llvm * Must build with PySide * Correct python version * Pass the branch to the docker build command * Correct typo * Switch to manylinux_2_28 * Works locally
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.