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

Installation on Rpi wth Python 3.11? #676

Open
StepanOzana opened this issue Jun 21, 2024 · 8 comments
Open

Installation on Rpi wth Python 3.11? #676

StepanOzana opened this issue Jun 21, 2024 · 8 comments

Comments

@StepanOzana
Copy link

Hello, have anyone tried installation on Rpi3 or Rpi4? I use them with Python 3.11.2 and Bullseye lite. Installation via pip just fails.

@t-sommer
Copy link
Contributor

An you share the error message?

@StepanOzana
Copy link
Author

I logged installation process in this file:

error_log.txt

@t-sommer
Copy link
Contributor

Can you try to run just python -m pip install fmpy (w/o [complete])?

@StepanOzana
Copy link
Author

sure, here is the result:
error_log2.txt

@StepanOzana
Copy link
Author

It seems like PyQt5 / PyQtWebEngine are the issues. Is there a way how to install it without them, at least as a temporary workaround? I don't need gui.

@t-sommer
Copy link
Contributor

You could try to hack the platform detection in __init__.py line 57 and add your processor:

if machine().lower() in {'aarch32', 'armv7l'}:
    platform += '32'
    architecture = 'aarch32'
elif machine().lower() in {'aarch64', 'arm64'}:
    platform += '64'
    architecture = 'aarch64'
elif machine().lower() in {'amd64', 'i386', 'i686', 'x86', 'x86_64', 'x86pc'}:
    if sys.maxsize > 2 ** 32:
        platform += '64'
        architecture = 'x86_64'
    else:
        platform += '32'
        architecture = 'x86'
else:
    raise Exception(f"Unsupported architecture: {machine()}")

@StepanOzana
Copy link
Author

Here is what I get after modifying init.py:
Failed to add logger proxy function. /usr/local/lib/python3.9/dist-packages/fmpy/logging/linux32/logging.so: cannot open shared object file: No such file or directory

@t-sommer
Copy link
Contributor

t-sommer commented Jul 3, 2024

You should still be able to simulate FMUs. The logging.so is only needed to process variadic arguments in log calls.

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