Improve README #2
Labels
Comments
|
I updated the README.md in the master branch. If you have other infos to add, do it. |
thepianoboy
added a commit
that referenced
this issue
Sep 10, 2019
* Add arch-llvm and centos builders * Fix arch llvm builder to not wait for I/O * Run tests after completion of build (hopefully) * Update CentOS to devtoolset-8 to fill coverage gap * Test manual deployment * Add FreeBSD builder, probably * Disable freebsd builder and fix arch tests * Update documentation and prepare for first merge * Use environment variables for declarations * Environment variables attempt 2 * Environment variables: Episode III * Environment variables: Episode IV * Environment variables: Episode V * Environment variables: Episode VI * Environment variables: Episode VI * Environment variables: Episode VII * Environment variables: Episode VIII * Environment variables: Episode IX * Disable FSI CI on Windows * Disable FSI on VS2017 and VS2015 to test builders * FreeBSD attempt #2 * Revert "FreeBSD attempt #2" This reverts commit c9483ec. * Add ubuntu builder * The ubuntu builder breaks things? * Ubuntu builder commit #3 * More ubuntu builder error detail * Maybe the entrypoint is bad? * It was the environment. Fix packages now * Ubuntu is frustrating * Missed a tar command * Ubuntu uses bad python * Add anaconda deployment * Fix wrong builder OS in deploy * conda-build should probably use mkdir -p * Arch docker is too big
thepianoboy
added a commit
that referenced
this issue
Sep 12, 2019
* Add arch-llvm and centos builders * Fix arch llvm builder to not wait for I/O * Run tests after completion of build (hopefully) * Update CentOS to devtoolset-8 to fill coverage gap * Test manual deployment * Add FreeBSD builder, probably * Disable freebsd builder and fix arch tests * Update documentation and prepare for first merge * Use environment variables for declarations * Environment variables attempt 2 * Environment variables: Episode III * Environment variables: Episode IV * Environment variables: Episode V * Environment variables: Episode VI * Environment variables: Episode VI * Environment variables: Episode VII * Environment variables: Episode VIII * Environment variables: Episode IX * Disable FSI CI on Windows * Disable FSI on VS2017 and VS2015 to test builders * FreeBSD attempt #2 * Revert "FreeBSD attempt #2" This reverts commit c9483ec. * Add ubuntu builder * The ubuntu builder breaks things? * Ubuntu builder commit #3 * More ubuntu builder error detail * Maybe the entrypoint is bad? * It was the environment. Fix packages now * Ubuntu is frustrating * Missed a tar command * Ubuntu uses bad python * Add anaconda deployment * Fix wrong builder OS in deploy * conda-build should probably use mkdir -p * Arch docker is too big * Add macOS Builder * macOS doesn't have wget * macOS has wget again, blaze too... * Apparently BLAZE_DIR is not what I thought it was
thepianoboy
added a commit
that referenced
this issue
Oct 10, 2019
* Add arch-llvm and centos builders * Fix arch llvm builder to not wait for I/O * Run tests after completion of build (hopefully) * Update CentOS to devtoolset-8 to fill coverage gap * Test manual deployment * Add FreeBSD builder, probably * Disable freebsd builder and fix arch tests * Update documentation and prepare for first merge * Use environment variables for declarations * Environment variables attempt 2 * Environment variables: Episode III * Environment variables: Episode IV * Environment variables: Episode V * Environment variables: Episode VI * Environment variables: Episode VI * Environment variables: Episode VII * Environment variables: Episode VIII * Environment variables: Episode IX * Disable FSI CI on Windows * Disable FSI on VS2017 and VS2015 to test builders * FreeBSD attempt #2 * Revert "FreeBSD attempt #2" This reverts commit c9483ec. * Add ubuntu builder * The ubuntu builder breaks things? * Ubuntu builder commit #3 * More ubuntu builder error detail * Maybe the entrypoint is bad? * It was the environment. Fix packages now * Ubuntu is frustrating * Missed a tar command * Ubuntu uses bad python * Add anaconda deployment * Fix wrong builder OS in deploy * conda-build should probably use mkdir -p * Arch docker is too big * Add macOS Builder * macOS doesn't have wget * macOS has wget again, blaze too... * Apparently BLAZE_DIR is not what I thought it was * WIP on windows deploy * Fix YAML error * Test conda environment setup * Use conda without activate * This ought to do it * Attempt Windows deploy * Attempt Windows deploy with workaround * I really messed up the anaconda install, try again * Update for new windows builders
thepianoboy
added a commit
that referenced
this issue
Dec 4, 2019
* Add arch-llvm and centos builders * Fix arch llvm builder to not wait for I/O * Run tests after completion of build (hopefully) * Update CentOS to devtoolset-8 to fill coverage gap * Test manual deployment * Add FreeBSD builder, probably * Disable freebsd builder and fix arch tests * Update documentation and prepare for first merge * Use environment variables for declarations * Environment variables attempt 2 * Environment variables: Episode III * Environment variables: Episode IV * Environment variables: Episode V * Environment variables: Episode VI * Environment variables: Episode VI * Environment variables: Episode VII * Environment variables: Episode VIII * Environment variables: Episode IX * Disable FSI CI on Windows * Disable FSI on VS2017 and VS2015 to test builders * FreeBSD attempt #2 * Revert "FreeBSD attempt #2" This reverts commit c9483ec. * Add ubuntu builder * The ubuntu builder breaks things? * Ubuntu builder commit #3 * More ubuntu builder error detail * Maybe the entrypoint is bad? * It was the environment. Fix packages now * Ubuntu is frustrating * Missed a tar command * Ubuntu uses bad python * Add anaconda deployment * Fix wrong builder OS in deploy * conda-build should probably use mkdir -p * Arch docker is too big * Add macOS Builder * macOS doesn't have wget * macOS has wget again, blaze too... * Apparently BLAZE_DIR is not what I thought it was * WIP on windows deploy * Fix YAML error * Test conda environment setup * Use conda without activate * This ought to do it * Attempt Windows deploy * Attempt Windows deploy with workaround * I really messed up the anaconda install, try again * Update for new windows builders * Add Doxygen deployment * Tweak ssh key import * Whoops, bad YAML * Add hostkey validation for Doxygen * Clean up arch image earlier in build Also, only clean up SSH keys in doxygen deploy where the file exists
thepianoboy
added a commit
that referenced
this issue
Dec 11, 2019
* Add arch-llvm and centos builders * Fix arch llvm builder to not wait for I/O * Run tests after completion of build (hopefully) * Update CentOS to devtoolset-8 to fill coverage gap * Test manual deployment * Add FreeBSD builder, probably * Disable freebsd builder and fix arch tests * Update documentation and prepare for first merge * Use environment variables for declarations * Environment variables attempt 2 * Environment variables: Episode III * Environment variables: Episode IV * Environment variables: Episode V * Environment variables: Episode VI * Environment variables: Episode VI * Environment variables: Episode VII * Environment variables: Episode VIII * Environment variables: Episode IX * Disable FSI CI on Windows * Disable FSI on VS2017 and VS2015 to test builders * FreeBSD attempt #2 * Revert "FreeBSD attempt #2" This reverts commit c9483ec. * Add ubuntu builder * The ubuntu builder breaks things? * Ubuntu builder commit #3 * More ubuntu builder error detail * Maybe the entrypoint is bad? * It was the environment. Fix packages now * Ubuntu is frustrating * Missed a tar command * Ubuntu uses bad python * Add anaconda deployment * Fix wrong builder OS in deploy * conda-build should probably use mkdir -p * Arch docker is too big * Add macOS Builder * macOS doesn't have wget * macOS has wget again, blaze too... * Apparently BLAZE_DIR is not what I thought it was * WIP on windows deploy * Fix YAML error * Test conda environment setup * Use conda without activate * This ought to do it * Attempt Windows deploy * Attempt Windows deploy with workaround * I really messed up the anaconda install, try again * Update for new windows builders * Add Doxygen deployment * Tweak ssh key import * Whoops, bad YAML * Add hostkey validation for Doxygen * Clean up arch image earlier in build Also, only clean up SSH keys in doxygen deploy where the file exists * Fix misnamed file * Use private key from file * File permissions again * Add clang to doxygen builder and prepare for PR
thepianoboy
added a commit
that referenced
this issue
Dec 16, 2019
* Add arch-llvm and centos builders * Fix arch llvm builder to not wait for I/O * Run tests after completion of build (hopefully) * Update CentOS to devtoolset-8 to fill coverage gap * Test manual deployment * Add FreeBSD builder, probably * Disable freebsd builder and fix arch tests * Update documentation and prepare for first merge * Use environment variables for declarations * Environment variables attempt 2 * Environment variables: Episode III * Environment variables: Episode IV * Environment variables: Episode V * Environment variables: Episode VI * Environment variables: Episode VI * Environment variables: Episode VII * Environment variables: Episode VIII * Environment variables: Episode IX * Disable FSI CI on Windows * Disable FSI on VS2017 and VS2015 to test builders * FreeBSD attempt #2 * Revert "FreeBSD attempt #2" This reverts commit c9483ec. * Add ubuntu builder * The ubuntu builder breaks things? * Ubuntu builder commit #3 * More ubuntu builder error detail * Maybe the entrypoint is bad? * It was the environment. Fix packages now * Ubuntu is frustrating * Missed a tar command * Ubuntu uses bad python * Add anaconda deployment * Fix wrong builder OS in deploy * conda-build should probably use mkdir -p * Arch docker is too big * Add macOS Builder * macOS doesn't have wget * macOS has wget again, blaze too... * Apparently BLAZE_DIR is not what I thought it was * WIP on windows deploy * Fix YAML error * Test conda environment setup * Use conda without activate * This ought to do it * Attempt Windows deploy * Attempt Windows deploy with workaround * I really messed up the anaconda install, try again * Update for new windows builders * Add Doxygen deployment * Tweak ssh key import * Whoops, bad YAML * Add hostkey validation for Doxygen * Clean up arch image earlier in build Also, only clean up SSH keys in doxygen deploy where the file exists * Fix misnamed file * Use private key from file * File permissions again * Add clang to doxygen builder and prepare for PR * Doxygen builds only on develop * Doxygen builds only on develop - fixed
thepianoboy
added a commit
that referenced
this issue
Mar 4, 2021
* Add arch-llvm and centos builders * Fix arch llvm builder to not wait for I/O * Run tests after completion of build (hopefully) * Update CentOS to devtoolset-8 to fill coverage gap * Test manual deployment * Add FreeBSD builder, probably * Disable freebsd builder and fix arch tests * Update documentation and prepare for first merge * Use environment variables for declarations * Environment variables attempt 2 * Environment variables: Episode III * Environment variables: Episode IV * Environment variables: Episode V * Environment variables: Episode VI * Environment variables: Episode VI * Environment variables: Episode VII * Environment variables: Episode VIII * Environment variables: Episode IX * Disable FSI CI on Windows * Disable FSI on VS2017 and VS2015 to test builders * FreeBSD attempt #2 * Revert "FreeBSD attempt #2" This reverts commit c9483ec. * Add ubuntu builder * The ubuntu builder breaks things? * Ubuntu builder commit #3 * More ubuntu builder error detail * Maybe the entrypoint is bad? * It was the environment. Fix packages now * Ubuntu is frustrating * Missed a tar command * Ubuntu uses bad python * Add anaconda deployment * Fix wrong builder OS in deploy * conda-build should probably use mkdir -p * Arch docker is too big * Add macOS Builder * macOS doesn't have wget * macOS has wget again, blaze too... * Apparently BLAZE_DIR is not what I thought it was * WIP on windows deploy * Fix YAML error * Test conda environment setup * Use conda without activate * This ought to do it * Attempt Windows deploy * Attempt Windows deploy with workaround * I really messed up the anaconda install, try again * Update for new windows builders * Add Doxygen deployment * Tweak ssh key import * Whoops, bad YAML * Add hostkey validation for Doxygen * Clean up arch image earlier in build Also, only clean up SSH keys in doxygen deploy where the file exists * Fix misnamed file * Use private key from file * File permissions again * Add clang to doxygen builder and prepare for PR * Doxygen builds only on develop * Doxygen builds only on develop - fixed * Add CMake Presets to simplify CI configuration * Windows has issues with CMake CLI syntax * Update for new macOS builder * I'm pretty sure that synchrono would work * Update windows presets * Fix MSVC 2017 toolkit build * Restore Ubuntu builder settings * CMake doesn't like `--build` with VS generator Co-authored-by: Colin Vanden Heuvel <colin.vandenheuvel@wisc.edu>
thepianoboy
added a commit
that referenced
this issue
Jul 25, 2021
* Add arch-llvm and centos builders * Fix arch llvm builder to not wait for I/O * Run tests after completion of build (hopefully) * Update CentOS to devtoolset-8 to fill coverage gap * Test manual deployment * Add FreeBSD builder, probably * Disable freebsd builder and fix arch tests * Update documentation and prepare for first merge * Use environment variables for declarations * Environment variables attempt 2 * Environment variables: Episode III * Environment variables: Episode IV * Environment variables: Episode V * Environment variables: Episode VI * Environment variables: Episode VI * Environment variables: Episode VII * Environment variables: Episode VIII * Environment variables: Episode IX * Disable FSI CI on Windows * Disable FSI on VS2017 and VS2015 to test builders * FreeBSD attempt #2 * Revert "FreeBSD attempt #2" This reverts commit c9483ec. * Add ubuntu builder * The ubuntu builder breaks things? * Ubuntu builder commit #3 * More ubuntu builder error detail * Maybe the entrypoint is bad? * It was the environment. Fix packages now * Ubuntu is frustrating * Missed a tar command * Ubuntu uses bad python * Add anaconda deployment * Fix wrong builder OS in deploy * conda-build should probably use mkdir -p * Arch docker is too big * Add macOS Builder * macOS doesn't have wget * macOS has wget again, blaze too... * Apparently BLAZE_DIR is not what I thought it was * WIP on windows deploy * Fix YAML error * Test conda environment setup * Use conda without activate * This ought to do it * Attempt Windows deploy * Attempt Windows deploy with workaround * I really messed up the anaconda install, try again * Update for new windows builders * Add Doxygen deployment * Tweak ssh key import * Whoops, bad YAML * Add hostkey validation for Doxygen * Clean up arch image earlier in build Also, only clean up SSH keys in doxygen deploy where the file exists * Fix misnamed file * Use private key from file * File permissions again * Add clang to doxygen builder and prepare for PR * Doxygen builds only on develop * Doxygen builds only on develop - fixed * Add CMake Presets to simplify CI configuration * Windows has issues with CMake CLI syntax * Update for new macOS builder * I'm pretty sure that synchrono would work * Update windows presets * Fix MSVC 2017 toolkit build * Restore Ubuntu builder settings * CMake doesn't like `--build` with VS generator * Fix truncated CMakePreset * Convert builders to Ninja, add colors * Update ubuntu builder version number * Fix ubuntu image tag and add more colors * Fix EIGEN_INCLUDE_DIR on Ubuntu * Change C++ version detection to use modern CMake (supported since 3.1) * Add Irrlicht dependency that APT misses in Ubuntu builder Co-authored-by: Colin Vanden Heuvel <colin.vandenheuvel@wisc.edu>
shlok191
added a commit
that referenced
this issue
Dec 13, 2021
shlok191
added a commit
that referenced
this issue
Dec 20, 2021
thepianoboy
added a commit
that referenced
this issue
Feb 9, 2022
* Add build for vs2019 toolset * Work around weird ninja behavior * Try VS generator * VS Generator won't build with the Ninja command, obviously * Swap toolset versions to correct VS versions * Added almalinux builder * Added python_module for almalinux * Added Python_Module testing for AlmaLinux #2 * Enabled module Pardiso_MKL for almalinux builder * Enabling Module Pardiso_MKL for Almalinux #2 * Fixed almalinux builder for module Pardiso_MKL * Configured windows builders to Release mode * Downgrade blaze to 3.7 in Windows 11 builder * Disable multicore in VS2022 (compiler bug) * Fixed almalinux's location for iomp5 library. * Turned off GPU for VS 2022 Co-authored-by: Colin Vanden Heuvel <colin.vandenheuvel@wisc.edu> Co-authored-by: Shlok Sabarwal <shlok190303@gmail.com>
thepianoboy
pushed a commit
that referenced
this issue
Feb 10, 2022
thepianoboy
pushed a commit
that referenced
this issue
Feb 10, 2022
thepianoboy
added a commit
that referenced
this issue
Mar 23, 2022
* Add arch-llvm and centos builders * Fix arch llvm builder to not wait for I/O * Run tests after completion of build (hopefully) * Update CentOS to devtoolset-8 to fill coverage gap * Test manual deployment * Add FreeBSD builder, probably * Disable freebsd builder and fix arch tests * Update documentation and prepare for first merge * Use environment variables for declarations * Environment variables attempt 2 * Environment variables: Episode III * Environment variables: Episode IV * Environment variables: Episode V * Environment variables: Episode VI * Environment variables: Episode VI * Environment variables: Episode VII * Environment variables: Episode VIII * Environment variables: Episode IX * Disable FSI CI on Windows * Disable FSI on VS2017 and VS2015 to test builders * FreeBSD attempt #2 * Revert "FreeBSD attempt #2" This reverts commit c9483ec. * Add ubuntu builder * The ubuntu builder breaks things? * Ubuntu builder commit #3 * More ubuntu builder error detail * Maybe the entrypoint is bad? * It was the environment. Fix packages now * Ubuntu is frustrating * Missed a tar command * Ubuntu uses bad python * Add anaconda deployment * Fix wrong builder OS in deploy * conda-build should probably use mkdir -p * Arch docker is too big * Add macOS Builder * macOS doesn't have wget * macOS has wget again, blaze too... * Apparently BLAZE_DIR is not what I thought it was * WIP on windows deploy * Fix YAML error * Test conda environment setup * Use conda without activate * This ought to do it * Attempt Windows deploy * Attempt Windows deploy with workaround * I really messed up the anaconda install, try again * Update for new windows builders * Add Doxygen deployment * Tweak ssh key import * Whoops, bad YAML * Add hostkey validation for Doxygen * Clean up arch image earlier in build Also, only clean up SSH keys in doxygen deploy where the file exists * Fix misnamed file * Use private key from file * File permissions again * Add clang to doxygen builder and prepare for PR * Doxygen builds only on develop * Doxygen builds only on develop - fixed * Add CMake Presets to simplify CI configuration * Windows has issues with CMake CLI syntax * Update for new macOS builder * I'm pretty sure that synchrono would work * Update windows presets * Fix MSVC 2017 toolkit build * Restore Ubuntu builder settings * CMake doesn't like `--build` with VS generator * Fix truncated CMakePreset * Convert builders to Ninja, add colors * Update ubuntu builder version number * Fix ubuntu image tag and add more colors * Fix EIGEN_INCLUDE_DIR on Ubuntu * Change C++ version detection to use modern CMake (supported since 3.1) * Add Irrlicht dependency that APT misses in Ubuntu builder * Update CMake Presets for upcoming Windows 11 builder * Update CMakePresets.json, contrib/.gitlab-ci.yml * Fix doxygen dependency check * Fix extra quote in CI script * Remove architecture in Ninja builder presets for Windows * FSI CMake broke again * Add build for vs2019 toolset * Work around weird ninja behavior * Try VS generator * VS Generator won't build with the Ninja command, obviously * Swap toolset versions to correct VS versions * Added almalinux builder * Added python_module for almalinux * Added Python_Module testing for AlmaLinux #2 * Enabled module Pardiso_MKL for almalinux builder * Enabling Module Pardiso_MKL for Almalinux #2 * Fixed almalinux builder for module Pardiso_MKL * Configured windows builders to Release mode * Downgrade blaze to 3.7 in Windows 11 builder * Disable multicore in VS2022 (compiler bug) * Fixed almalinux's location for iomp5 library. * Turned off GPU for VS 2022 * Update macOS builder to Monterey * Fix yaml error * More yaml dependencies * Added MacOS M1 presets CI configuration * Set module flags for MacOS M1 CI presets * Fixed MacOS M1 presets * Added CI configuration for MacOS with Apple silicon * Merge CMake Presets for Intel and Apple Silicon * Temporarily disable macOS x86 builder Co-authored-by: Colin Vanden Heuvel <colin.vandenheuvel@wisc.edu> Co-authored-by: Shlok Sabarwal <shlok190303@gmail.com> Co-authored-by: Shlok Sabarwal <shlok@euler-login-1.wacc.wisc.edu> Co-authored-by: builder <builder@builders-Mac.local>
shlok191
added a commit
that referenced
this issue
Apr 5, 2022
shlok191
added a commit
that referenced
this issue
Apr 11, 2022
shlok191
added a commit
that referenced
this issue
Apr 11, 2022
* use our own PI instead of math_constant.h * no need to include cub.cuh * Add function GetNumParticleAboveZ to GPU module * Fix a bug where C::GPU won't pick up triangles when particle radii are small * Add first draft of emscripten build instructions * Add some reporting functions from vehicle models: - force/torque in tracked vehicle suspension - overall track length * Rename class to address multiply defined symbols in SWIG * Update Chrono project configuration script to generate CMake lists for the compile and link flags * Update google benchmark * The ChModalAssembly::GetStateLocal(), previously GetStateIncrement(), now returns also the speed of the coordinates of the reduced subassembly. * If a nonzero damping matrix is used in ChModalAssembly, then it is used in dynamics. The internal formces account also for damping effect. * More getters in ChModalAssembly, for diagnostics and readability of API. * New classes that define various models for generating the damping matrix R^ of the reduced subassembly. To be used when doing myassembly->SwitchModalReductionON() At the moment I created: ChModalDampingNone() // no damping (also default) ChModalDampingReductionR(*my_assembly) // transforms the original damping matrix of the full subassembly ChModalDampingReductionR(full_R_ext) // transforms an externally-provided damping matrix of the full subassembly ChModalDampingCustom(reduced_R_ext) // uses an externally-provided damping matrix of the reduced subassembly ChModalDampingRayleigh(0.01, 0.05) // generates a damping matrix from reduced M ad K using Rayleygh alpha-beta ChModalDampingFactorRmm(zetas) // generates a damping matrix from damping factors zetas of dynamic modes ChModalDampingFactorRayleigh(zetas,a,b) // generates a damping matrix from damping factors of dynamic modes and rayleigh a,b for boundary nodes ChModalDampingFactorAssembly(zetas) // generates a damping matrix from damping factors of the modes of the subassembly, including masses of boundary * Support for the new damping models. * The Lanczos and Krylov solvers have some contstraints on size, n. of eigenvalues, parameter m. Enforce them when computing m. * Some changes in the modal demo, to test new features. Also improve display. Also move cantilever in vertical plane to see it better. * Update change log with entry for patch release 7.0.2 * Show the damping factor in Irrlicht GUI, if different from zero. Just for quick tests of ComputeModesDamped(). Also do not shot Hz for modes not available. * Redesigned storage metho for eigenvalue analysis. The function ComputeModes() and ComputeModesDamped() functions can be called even after an assembly has been converted into a reduced modal assembly via SwitchModalReductionON(). Previously these two functions worked only for unreduced assembly. In this way now we can treat the reduced modal assembly as a black box for whome we may be interested in getting eigenvalues and eigenvectors. Results of these Compute functions go into dedicated data structures that won't be used later even if after a SwitchModalReductionON. * Added debug code. Added an assert() to avoid someone using a not-ready feature. * Updated demo for testing modal reduction. * Update visualization meshes (OBJ+MTL) for the M113 vehicle * Created new branch for mac-intel ci build scripts * Restarting the macOS intel builder * Restarting the macOS intel builder * Re-deploying MacOS-intel builder * Attempting to Re-deploying MacOS-intel builder #2 * Revert "Re-deploying MacOS-intel builder" This reverts commit 1e30bba. Co-authored-by: LuningFang <lfang9@wisc.edu> Co-authored-by: Ruochun Zhang <rzhang294@euler-login-2.wacc.wisc.edu> Co-authored-by: Ruochun Zhang <rzhang294@euler-login-1.wacc.wisc.edu> Co-authored-by: Colin Vanden Heuvel <colin.vandenheuvel@wisc.edu> Co-authored-by: Radu Serban <serban@wisc.edu> Co-authored-by: tasora <tasora@ied.unipr.it>
shlok191
added a commit
that referenced
this issue
Apr 14, 2022
* Removing linking libiomp5.lib for vs 2019 deployment * Implemented build_pychrono.bat code in gitlab-ci.yml * Fixed .gitlab-ci.yml for windows deployment * Fixing windows deployment CI script * Made changes to gitlab-ci.yml file * Edited .gitlab-ci.yml to fix vs2019 deploy script * Attempting conda build with conda-forge channel for vs2019 deploy * Changed bld.bat to fix environment variables * Edited meta.yaml for vs2019 deployment * Attempting to run vs2019 deployment with correct vs compiler version * Attempting to run vs2019 deployment with correct vs compiler version * Attempt to use vs2019 for windows:vs2019 deployment * Attempt to fix vs2019 #2 * Attempt to fix vs2019 #3 * Attempt to fix vs2019 #3 * Attempt to fix vs2019 #4 * Attempt to fix vs2019 #4 * Attempt to fix vs2019 #5 * Change windows conda compiler * Attempt to fix vs2019 #6 * Attempt to fix vs2019 #7 * Attempt to fix vs2019 #8 * Attempt to fix vs2019 #9 * Attempt to fix vs2019 #10 * Attempt to fix vs2019 #11 * Attempt to fix vs2019 #12 * Attempt to fix vs2019 #12 * Attempting vs2019 deployment for windows without irrlcith * Attempt to fix vs2019 #13 * Attempt to fix vs2019 #14 * Attempting to get vs2019 deployment to pick correct location for Irrlicht * Revert "Attempting to get vs2019 deployment to pick correct location for Irrlicht" This reverts commit bea088d. * Attempt to fix vs2019 #15
shlok191
added a commit
that referenced
this issue
Apr 26, 2022
shlok191
added a commit
that referenced
this issue
May 2, 2022
shlok191
added a commit
that referenced
this issue
May 28, 2022
shlok191
added a commit
that referenced
this issue
Jun 5, 2022
shlok191
added a commit
that referenced
this issue
Jun 5, 2022
shlok191
added a commit
that referenced
this issue
Jun 5, 2022
shlok191
added a commit
that referenced
this issue
Jun 11, 2022
shlok191
added a commit
that referenced
this issue
Jun 12, 2022
shlok191
added a commit
that referenced
this issue
Jun 25, 2022
shlok191
added a commit
that referenced
this issue
Jun 26, 2022
shlok191
added a commit
that referenced
this issue
Jun 27, 2022
shlok191
added a commit
that referenced
this issue
Jun 29, 2022
shlok191
added a commit
that referenced
this issue
Jul 3, 2022
shlok191
added a commit
that referenced
this issue
Jul 17, 2022
shlok191
added a commit
that referenced
this issue
Aug 9, 2022
shlok191
added a commit
that referenced
this issue
Aug 17, 2022
shlok191
added a commit
that referenced
this issue
Aug 24, 2022
shlok191
added a commit
that referenced
this issue
Sep 3, 2022
shlok191
added a commit
that referenced
this issue
Sep 19, 2022
shlok191
added a commit
that referenced
this issue
Sep 19, 2022
shlok191
added a commit
that referenced
this issue
Sep 24, 2022
shlok191
added a commit
that referenced
this issue
Sep 26, 2022
shlok191
added a commit
that referenced
this issue
Oct 1, 2022
shlok191
added a commit
that referenced
this issue
Oct 25, 2022
shlok191
added a commit
that referenced
this issue
Nov 1, 2022
shlok191
added a commit
that referenced
this issue
Nov 3, 2022
shlok191
added a commit
that referenced
this issue
Nov 26, 2022
shlok191
added a commit
that referenced
this issue
Dec 26, 2022
shlok191
added a commit
that referenced
this issue
Feb 21, 2023
shlok191
added a commit
that referenced
this issue
Feb 27, 2023
shlok191
added a commit
that referenced
this issue
May 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current README would serve better as release notes.
A new readme with info about the project, quickstart on how to use Chrono, and links to documentation needs to be written.
The text was updated successfully, but these errors were encountered: