![]() ![]() The biggest work is usually to make it adapt to a new MacOS major version.Īnother slightly trickier job will be to add and verify the according ARM llvm backend to let it compile the VIs to native M1 assembly code. This could proof a little troublesome but the LabVIEW source code being compiled in at least three different compilers currently xcode, gcc and Visual C, should have ironed out most compiler specific throuble. They need to fix a few things that have more to do with Mac OS Big Sur than anything else and then recompile everything in a recent xcode version for the ARM. As far as LabVIEW is concerned it is certainly a fairly doable task. As to when LabVIEW fully will support Mac M1 hardware my guess is as good as yours. ![]() It still requires tinkering with some MacOS settings for your executable. Hardware drivers require kernel drivers and Apple choose to not support virtualization through Rosette2 for kernel code, most likely because they wanted to have it running in this decade. The official news is that it does not work, the unofficial news is that it can be made to work if you only want LabVIEW but no drivers of any sort. Since the Beta has expired, the according forum has been closed. Can LabView run on Mac computers with the M chip or not? If not, will be solved soon, or is LabView abandoning the Mac platform? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |