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

Fixes needed for Raspberry PI build on latest Raspbian #2281

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

ericnelsonaz
Copy link

These updates are needed in order to build on the latest version of Raspberry PI O/S.

Commit 7fcd7f7 changed this method.

Signed-off-by: Eric Nelson <[email protected]>
Without this, we get an undefined symbol at link time.

Signed-off-by: Eric Nelson <[email protected]>
@matteblair matteblair self-requested a review July 31, 2021 20:27
The Url::resolve() calls in main.cpp appear to be backwards and should
add the current working directory to the base (file://) instead of the
reverse.

Signed-off-by: Eric Nelson <[email protected]>
Without this, I saw lockups that prevented additional characters from being read
in the getKey() routine.

Signed-off-by: Eric Nelson <[email protected]>
Copy link
Member

@matteblair matteblair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the URL fixes!

The getKey() changes didn't seem to make any difference on my Pi. My keyboard inputs are being ignored both with and without this change. But if this change helps for you then let's keep it!

I'd ask that you change the library configuration that I commented on, then this will be good to merge.

@@ -40,6 +40,7 @@ target_link_libraries(tangram
/opt/vc/lib/libbrcmGLESv2.so
/opt/vc/lib/libvchiq_arm.so
/opt/vc/lib/libvcos.so
/usr/lib/arm-linux-gnueabihf/libatomic.so.1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using just atomic here seems to work on my pi. If it works on yours too, can you replace the path here with atomic? I'd rather not hard-code libraries where it isn't necessary.

@ETE-Design
Copy link

@matteblair Is it possible to use Tangram-es as an Navigation System with Route Directions on an Raspberry Pi 4?

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

Successfully merging this pull request may close these issues.

3 participants