llnl / llnl/LEAP

Inconsistency in makefile and python code

Open
#185 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Cuda
Stars
249
Forks
37
PR merge metrics
No merged PRs in 30d

Description

Hello,

I'm really enjoying this library. I recompiled the library.

I noticed that it compiles the source object "libprojectors.so" instead of "libleapct.so" that the python code uses with ctypes. It worked when changing the name, so I assume they are the same.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Inspect the Makefile and the Python code that uses ctypes to compare the built library name with the name loaded at runtime. Confirm the intended name, make the build and Python reference consistent, then rebuild the library and verify that the Python import succeeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.