> this is really unfair from national as VIs can migrate from one platform > to another > and embedding VIs in multiples "standalone engine" (one for each > platform) should be quite easy to do.
VIs are source code. Exes are a produced image of the source code. While it wasn't easy making platform independent layers so that your souce code could move between platforms, it is even more difficult to crosscompile VIs for a different processor alignment, and byte ordering. As I said, we now have that product for RT, and it costs money. In fact, this is also what the PDA tool has to do, and it also costs money. If/when this is available for other platforms, it will not really make fat binaries, but will be able to make binaries for other types of machines. Again, this will most likely be something you purchase and add to your mac so that it can make windows EXEs without having to sit at a PC. So, it would be easier if LV were interpretted, but since it is compiled, you need your compiler to run on a Mac. Of course if you want to buy Virtual PC and LV for Windows, then it really is easy, and fair. Greg McKaskle
