Skip to content
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

ChNodeBody.h path #12

Closed
jcmadsen opened this issue Dec 26, 2013 · 1 comment
Closed

ChNodeBody.h path #12

jcmadsen opened this issue Dec 26, 2013 · 1 comment

Comments

@jcmadsen
Copy link
Contributor

moving ChNodeBody.h from ../physics to ../unit_FEM causes a compiler error on windows on two demos,
demos/fem/demo_meshless.cpp
demos/irrlicht/demo_sph.cpp

should probably generalize ChNodeBody to work with any object that can be constrained to a rigid body, not just FEM nodes, and have ChNodeBody.h implement that base class.

@tasora
Copy link
Member

tasora commented Dec 27, 2013

Fixed.
those two demos really did not need that header, and I forgot to
update their source when I moved the ChNodeBody class into unit_FEM.

By the way, Justin: you're right about making ChNodeBody a more
'polymorphic' class, but for the moment I am keeping it in this way,
even if the class hierarchy is suboptimal, because I have to do quick
tests with core FEM algorithms before proceeding to smarter class
inheritance diagrams (and also the name ChNodeBody might be changed too)

bye
Alessandro

Il 26/12/2013 17:41, Justin Madsen ha scritto:

moving ChNodeBody.h from ../physics to ../unit_FEM causes a compiler
error on windows on two demos,
demos/fem/demo_meshless.cpp
demos/irrlicht/demo_sph.cpp

should probably generalize ChNodeBody to work with any object that can
be constrained to a rigid body, not just FEM nodes, and have
ChNodeBody.h implement that base class.


Reply to this email directly or view it on GitHub
#12.

@tasora tasora closed this as completed Dec 27, 2013
shlok191 added a commit that referenced this issue Apr 12, 2022
shlok191 added a commit that referenced this issue Apr 12, 2022
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
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

No branches or pull requests

2 participants