Hi Zet, Thanks for testing this and sharing your results.
There is a reason for not changing the file name and that is that when you install a new Jallib version and you are using JALEdit or JALIDE you do not have to change anything since the compiler name remains the same. Next to that quite some Python scripts use the JAL compiler for verification and release and we do not want to change the scripts for every version change of the compiler. As you know the compiler shows its version when you use it: jal jalv25r3 (compiled Sep 15 2019). Again, thank for sharing the info and your suggestion. Kind regards, Rob ________________________________ Van: [email protected] <[email protected]> namens Zet Weeh <[email protected]> Verzonden: zaterdag 9 november 2019 23:44 Aan: jallib <[email protected]> Onderwerp: [jallib] Re: Looking for beta testers of the Windows JAL Compiler Hi Rob I tested the 32 and 64 version on two different computers with W10-32 bit and W10-64 bit. I used 3 JAL programs on each computer with blinking leds, PWM and writing to a memory chip. All was working well and without problems. I have a suggestion about the name. I understand this is a totaly new build. So call it 'jalv3_32' and 'jalv3_64'. So it is clear for everybody that this is the latest version. Kind regards, Peter Op dinsdag 10 september 2019 19:20:21 UTC+2 schreef Rob: Hello JAL users, I am looking for people that want to test the new version of the JAL compiler under Windows (Linux is also allowed if you want to play with it). Main reason is that I compiled the compiler using a different c-compiler. This because the current JAL 32-bit Windows compiler shows random (but still correct) behavior assigning variables to data space. Since it is only for the 32-bit version I suspected Visual Studio with which I create the new JAL compiler. So I recompiled the JAL compiler sources for Windows with a different c-compiler and that fixed the problem so my plan is to compile the JAL compiler using this c-compiler. In order not to mix up things too much I used for these compilers the same names as are used for the Linux versions but they have the extension '.exe': jalv2-i686.exe : Newly created Windows 32-bit binary jalv2-x86-64.exe : Newly created Windows 64-bit binary You can find the compilers here: https://github.com/jallib/jalv2compiler/tree/master/bin What you will also see is that these compiler are smaller in size than their Visual Studio counterparts (jalv2.exe and jalv2_64.exe). As I mentioned earlier this version of the compiler also fixed this issue: https://github.com/jallib/jalv2compiler/issues/8 If you are testing it let me know if it works or not. Thanks for your help. Kind regards, Rob -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/a2c4945d-14ee-488d-b6f0-18fd7a692755%40googlegroups.com<https://groups.google.com/d/msgid/jallib/a2c4945d-14ee-488d-b6f0-18fd7a692755%40googlegroups.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/AM0PR07MB494876979E3F0FAB02CC5629E6750%40AM0PR07MB4948.eurprd07.prod.outlook.com.
