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

Infer libmesh build type in FindLIBMESH.cmake #4

Open
RonRahaman opened this issue Oct 29, 2020 · 2 comments
Open

Infer libmesh build type in FindLIBMESH.cmake #4

RonRahaman opened this issue Oct 29, 2020 · 2 comments

Comments

@RonRahaman
Copy link

I noticed that FindLIBMESH.cmake always tries to find the "opt" configuration of libmesh . Could you infer this from the user?

In many places, the libmesh and MOOSE stack use the environment variable "METHOD", which is either "opt", "oprof", or "dbg"

find_path(LIBMESH_PC NAMES libmesh-opt.pc
          HINTS ${LIBMESH_DIR} $ENV{LIBMESH_ROOT}
          PATHS ENV LD_LIBRARY_PATH
          PATH_SUFFIXES lib/pkgconfig pkgconfig
          NO_DEFAULT_PATH)
@pshriwise
Copy link
Owner

Hiya! I take it you’re looking one of the libmesh branches here?

Given that OpenMC could be built with libmesh independently of MOOSE, we probably want to have some default option here but yeah we could certainly look into that. Hard-coding libmesh-opt.pc was a temporary measure while I sorted out some issues with the libmesh pkgconfig files (libMesh/libmesh#2682). Now that these are incorporated in the latest libmesh release I can revisit how to approach this.

@pshriwise
Copy link
Owner

It's good timing that you brought this up, really, I was just starting to clean up some of libMesh related stuff in the libmesh_umesh2 branch yesterday. Right now I just rely on the libmesh.pc, which after that PR above should always be valid.

8566e2e

pshriwise pushed a commit that referenced this issue Feb 8, 2023
…shes

Centre for cylinder spherical meshes
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