Build error occurred in arm architecture about edge-home-orchestration-go HOT 10 CLOSED

@MoonkiHong I reproduced this issue and as I wrote earlier (and created a commit) it would be correct for each platform to create its own Dockerfile (This will solve the current problem).
P.S. Without creating a separate configuration for each hardware platform, we will greatly complicate our build machine.

from edge-home-orchestration-go.

@MoonkiHong I can fix this problem today. When have you Coconut release?
Of course a new build system can be proposed later (this task takes more time)

from edge-home-orchestration-go.

@MoonkiHong I will try to do this today so that the Coconut release will be without this issue. And also today I will eliminate one more inaccuracy with the documentation, which arose with the last commits. These will be different commits

from edge-home-orchestration-go.

@tdrozdovsky Just for the checker, we can successfully build the package for arm without any code modification w.r.t. the proper guidance from
https://www.stereolabs.com/docs/docker/building-arm-container-on-x86/, which means to apply a revision of the build environment. What about guiding this script properly in the regarding document then? (instead of a separate build system design)

@t25kim Thank you for your another great suggestion and evaluation for this issue! (including the self build validation w.r.t. the guidance as well)

from edge-home-orchestration-go.

@MoonkiHong I have prepared changes to fix this issue, but still need to test. When everything is ready, I will create a PR.

from edge-home-orchestration-go.

In the end, this is related to the general policy to support the platform extension, that I raised as #127. @tdrozdovsky Any thought about this?

from edge-home-orchestration-go.

@MoonkiHong I reproduced this issue and as I wrote earlier (and created a commit) it would be correct for each platform to create its own Dockerfile (This will solve the current problem).
P.S. Without creating a separate configuration for each hardware platform, we will greatly complicate our build machine.

@tdrozdovsky Makes sense. What about considering the design of resolution after the Coconut release from yours?

from edge-home-orchestration-go.

@tdrozdovsky Coconut release is by the end of October, this month. Let us start to resolve this issue from November. Thank you.

from edge-home-orchestration-go.

@MoonkiHong I will try to do this today so that the Coconut release will be without this issue. And also today I will eliminate one more inaccuracy with the documentation, which arose with the last commits. These will be different commits

@tdrozdovsky Really appreciate your passionate contribution!

from edge-home-orchestration-go.

@tdrozdovsky Just for the checker, we can successfully build the package for arm without any code modification w.r.t. the proper guidance from
https://www.stereolabs.com/docs/docker/building-arm-container-on-x86/, which means to apply a revision of the build environment. What about guiding this script properly in the regarding document then? (instead of a separate build system design)

from edge-home-orchestration-go.