add support for aarch64 #792

[yk-fujii]

Status

DEVELOPMENT

Description

This PR support to aarch64. autowarefoundation/autoware_ai#972
Included:

• Added documents to build autoware with drivepx2.
• Fixed a CMakeLists.

Todos

Steps to Test or Reproduce

Install with reference to documents.

[yk-fujii]

Since this can be confirmed only in a limited environment, I will check it myself.

[dejanpan]

alternatively we could ask on the slack "general" or autoware google group if there are any people with drivePX2 willing to test this.

[asimay]

Hi, dear friend. I'm doing PX2 testing now.
I'm willing to reflect testing result to you as my honor.
but can you help me on what's testing feature you want to do ?
and the first big issue is , PX2 has very small memory, only 6.5G , now it is very slow to run... any hint?

[asimay]

comments:
line 67 should be remove. it report error when setup.

git checkout -b aarch64 origin/feature/aarch64

and on kinetic version, ROS rviz has a big issue, especially for autoware, often shows tons of following err and exit:
0x141fda0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x4fbb10) ): Attempt to set a screen on a child window.
0x13f96e0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x4fbb10) ): Attempt to set a screen on a child window.

please see this link:
ros-visualization/rviz#1070

[czluck]

comments:
line 67 should be remove. it report error when setup.

git checkout -b aarch64 origin/feature/aarch64

and on kinetic version, ROS rviz has a big issue, especially for autoware, often shows tons of following err and exit:
0x141fda0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x4fbb10) ): Attempt to set a screen on a child window.
0x13f96e0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x4fbb10) ): Attempt to set a screen on a child window.

please see this link:
ros-visualization/rviz#1070

Hi, asimay , have you ever solved this problem ? I got the same issue yesterday

[gbiggs]

Thanks for using Autoware and for your question. However the issue tracker is for posting confirmed bugs and feature requests.

We ask that you please ask questions at the ROS Answers website following our support guidelines: https://gitlab.com/autowarefoundation/autoware.ai/autoware/wikis/Support-guidelines#ros-answers. Please pay particular attention to the information we ask you to provide.