

Einhugur Plugins on Xojo 2015r3 compiling 64 bit and for Raspberry PI Its been long time since my confidence level has been this high for a Xojo release and future roadmap. To me the impressing bits of 2015r3 are easily enough to make me confident that the next release will target some of that and make it both impressing and solid. I am confident that next release will continue on the right path and impress us. But if project was to jump from 15 to 200 mb then we would see programmers jumping board pretty fast. Same goes for compile sizes, many stopped using Windows builds when the ICU libraries added a lot to the build size, and they were only 20-30 mb addition.

With that said then how they continue is going to be critical of course as it is true that 64 bit without debugging is a bit of a teaser and not development tool to rely on. Having been playing with it throughout the alpha and beta process then for me then I am actually impressed, there are a lot fewer issues than I expected and overall things have just been a lot smoother than could have hoped for. Of course its not perfect and some would say its no good because of lack of debugging, to big compile sizes and because there might be bugs. So it's probably best to start a new branch called "universal" where you start making the 64 bit changes using CGFloat and add a note to the Readme explaining that one need to use Xojo 2016r1 (or whenever that type got added).This is great day in history of Xojo and for most Xojo developers. But that means that you cannot build macoslib with older Xojo versions any more, then. So, if you want to make macoslib compile on both 32 and 64 bit, you need to use this type where currently a Single is used and Apple uses CGFloat. Only recently Xojo added a CGFloat type to handle this. That type is Single on 32 bit and Double on 64 bit.

If it's UInteger, match that, too.Īnd for access into memoryblocks, see the code where SizeOfInteger is used as an example, and make sure it's used everywhere that way.Ī slightly more complicated problem are types where Apple uses CGFloat.

E.g, if the type is UIn32, then you need to match that even on 64 bit. h files), see which parameters are used, and make sure the same type is used on the declare. For every declare, find the original documentation (using Apple developer website or the header.
