# Multi-platform support of Julia (Power/Arm/Intel)

**URL:** <https://discourse.julialang.org/t/multi-platform-support-of-julia-power-arm-intel/1449>\
**Category:** Internals & Design\
**Created:** [January 12, 2017, 7:46pm UTC](https://discourse.julialang.org/t/multi-platform-support-of-julia-power-arm-intel/1449 "2017-01-12T19:46:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ppalmes](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ppalmes/32/6838_2.png) [@ppalmes](https://discourse.julialang.org/u/ppalmes)\
**Post date:** [January 12, 2017, 7:46pm UTC](https://discourse.julialang.org/t/multi-platform-support-of-julia-power-arm-intel/1449/1 "2017-01-12T19:46:57Z")

</div>

In some cluster environment, it’s typical to have Julia running in different hardware (Power/Intel/Arm) but using the same $HOME directory.

To support this multi-platform environment, $HOME/.julia/version only differentiates across Julia versions but not across Julia hardware supports. I suggest that the directory structure in $HOME/.julia should include the hardware: $HOME/.julia/version/power or $HOME/.juila/version/intel. This would avoid compiled objects in one hardware running in another hardware.

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ihnorton/32/26_2.png) [@ihnorton](https://discourse.julialang.org/u/ihnorton)\
**Post date:** [January 12, 2017, 10:02pm UTC](https://discourse.julialang.org/t/multi-platform-support-of-julia-power-arm-intel/1449/2 "2017-01-12T22:02:35Z")

</div>

There is a proposal and ongoing discussion about the future of the package manager [here](https://github.com/JuliaLang/Juleps/blob/master/Pkg3.md). I would suggest to open [an issue](https://github.com/JuliaLang/Juleps/issues) with your suggestion.