Ok. Unfortunately emulation/simulation is not an option for me (trying to write something against a GPU that I don't have locally.) Thanks for the info though.
Kenny On Friday, August 3, 2018 at 1:43:56 PM UTC-4, Ian Lance Taylor wrote: > > On Fri, Aug 3, 2018 at 8:06 AM, <y2k...@gmail.com <javascript:>> wrote: > > > > Are there any recommendations on developing on one architecture while > > deploying on another? For example, the target application is to be run > on > > arm or on machines with more exotic hardware configurations while my > > development environment is an x86 laptop. Are there better ways to do > > iteration beyond scping/rsyncing the go code from the dev environment > into > > the target? > > Depending on the target hardware, and the nature of the program, it's > sometimes faster to use QEMU or some other simulator or emulator to > run the target program than it is to actually copy the file to the > (typically much slower) real hardware. Of course you must test on the > real hardware at some point, but during iterative development QEMU can > be faster in some cases. > > Ian > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
