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

Errors compiling solver #94

Open
roooots opened this issue Jan 24, 2022 · 2 comments
Open

Errors compiling solver #94

roooots opened this issue Jan 24, 2022 · 2 comments

Comments

@roooots
Copy link

roooots commented Jan 24, 2022

Hi all,

after successfully running one of the RapidCFD tutorial cases, I tried compiling the interPhaseChangeFoam solver.
In the ../RapidCFD-dev/applications/solvers/multiphase/interPhaseChangeFoam/ folder I tried wmake but got errors about missing include files (phaseChangeTwoPhaseMixture.H, turbulenceModel.H, ...) so I copied these from the corresponding RapidCFD-dev/src/ folders.
However, now I'm getting different errors shortly after starting the compile: haseChangeTwoPhaseMixture/newPhaseChangeTwoPhaseMixture.C:59:5: error: ‘componentsConstructorTable’ is not a class, namespace, or enumeration
and many more.

Any suggestions what went wrong? Specifically, which environmental variables / paths are important to set before trying to compile the solvers?

Thanks,
r.

@TonkomoLLC
Copy link
Contributor

Hello,

Looking at the Allwmake file, I think RapidCFD is not setup for use with interPhaseChangeFoam. There are only two multiphase solvers that are setup for compilation:

wmake all solvers/multiphase/interFoam $*
wmake all solvers/multiphase/driftFluxFoam $*

I do not know the technical reason why interPhaseChangeFoam is not intended to compile, but I am pretty sure it is not by mistake (e.g., maybe some part of the interPhaseChangeFoam solver source code was not ported to the GPU).

But I do confirm that if you run ./Allwmake in applications/solvers/multiphase/interPhaseChangeFoam there are a number of compilation errors. I do not have a quick fix for you, unfortunately.

Best regards,

Eric

@roooots
Copy link
Author

roooots commented Jan 25, 2022

Thanks for your quick reply and your confirmation, though this was not the kind of answer I was hoping for ;-)

I will do some more research as to what options I currently have to get it running.

Thanks,
r.

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