Java Development on an Apple M1 – A One Year Review

Re:Java Development on an Apple M1 – A One Year Review by cedricziel on Friday March 25, 2022 @06:52AM (#30800574)

I'm a bit surprised nobody mentions the `--platform` argument that docker accepts to emulate a different architecture per container. It's a very smooth experience if you're reliant on 3rd party images.

Available through compose as well.

[ Parent | on HN ]

Re:Java Development on an Apple M1 – A One Year Review by spyremeown on Friday March 25, 2022 @08:06AM (#30801109)

I worked with cross-compiling containers. The compiling times were... bad. Our x86 build took like, two minutes (this was a very small and lean C++ application). The arm32v7 ones took upwards of 30 minutes.

[ Parent | on HN ]

Re:Java Development on an Apple M1 – A One Year Review by heffer on Friday March 25, 2022 @12:46PM (#30804386)

Works the other way around as well: Compile platform independent code (such as Java) on --platform=$BUILDPLATFORM in a build stage and then copy into containers that are --platform=$TARGETPLATFORM. That way your build only runs once, natively, but you can produce the correct runtime containers for each architecture rather quickly.

[ Parent | on HN ]

Re:Java Development on an Apple M1 – A One Year Review by the_svd_doctor on Friday March 25, 2022 @09:33AM (#30801945)

Same experience. Beefy machine, takes 45 minutes to compile cmake using a ppc64le container on an x86_64 host.

[ Parent | on HN ]