

- #Purebasic sprite maximum size mac osx#
- #Purebasic sprite maximum size install#
- #Purebasic sprite maximum size upgrade#
- #Purebasic sprite maximum size full#
- #Purebasic sprite maximum size software#
This entry was posted in Compiler, Uncategorized on Augby Fred. Keep in mind I got a very old CPU (Core i7 860 from 2009) and as discussed previously, just swapping the C compiler could lead to dramatic improvements.Īll in all, it’s very good news, and we are looking forward to fix the last remaining showstoppers and creating a beta version for all the OS, including may be some new like Raspberry ! The only noticeable change is the compilation time, which jumps from 5 secs on the ASM back-end to a whooping 24 secs on the C back-end (based on GCC) with the debugger on and optimisation disabled. The plan is to be able to switch seemlessly from ASM to C back-end and be able to compile the IDE on new platform, like Raspberry or OS X M1. So what’s the functional changes ? Well, nothing.
#Purebasic sprite maximum size software#
This is a big deal: the IDE is a very large software of about 130 000 lines of PureBasic code and using a lot of different features of the language. It tooks quite a lot of iteration with the alpha testers (and thanks to all of you all btw) to iron major issues, but here we are: the IDE is mostly working when compiled with the C back-end. This is the milestone we waited to validate the C back-end. Sneak peak into new CPU support for C back-end
#Purebasic sprite maximum size mac osx#
This entry was posted in Compiler, Mac OSX on Octoby Fred. It does feel a bit weird for me, but I know it will do the job just fine to build your cool apps on new Macs ! This will be the first version of PureBasic shipped without an assembly back-end.
#Purebasic sprite maximum size full#
Two more days and the whole compiler test suits was working which was amazing ! There is indeed some more work to do to build the full package, as some libraries needs to be tuned (missing headers due to new Cocoa SDK mainly), build scripts adjusted and so on, but it does looks very bright. Everything compiled out of the box and the first running executable was created after half day. I expected some adjustements to do here and here, but there were actually zero. This promised to be exciting, as the C toolchain isn’t based on gcc but on clang/LLVM.
#Purebasic sprite maximum size install#
Needed to install homebrew for subversion (I know, I know) and I finally started hacking the compiler. Seems to be known issue if I believe all the posts found on Reddit.

It tooks over 4 (four !) hours to install (after downloading). It was the longest installation I never experienced, at a point I though the Mini was broken. All seems smooth so far, a very quiet computer in a small form factor.Īfter a few minutes toying with the prefs to plugin my PC keyboard and Monitor on a KVM switch, I was ready to start to dev, and downloaded XCode. A quick look at the Task Monitor and we can see all the programs running on an ‘Apple’ CPU. First boot looks very familiar, you can’t really tell there is a new processor here. Last week, I bought a new Mac Mini to be able to port PureBasic on the new Apple M1 chip. This entry was posted in Linux, Releases on Novemby Fred. These 3 new build servers are already up and running, we hope it will solve some of the issues related to the Linux version of PureBasic !
#Purebasic sprite maximum size upgrade#
What does it means for you, PureBasic programmer ? It should be be easier to choose your dev environment (basically stick to Ubuntu LTS and upgrade it when a new version is released) and the produced executable should run on a wide range of Linux distros (you can even choose to build 2 versions, one on 18.04 LTS, and one on 20.04 LTS if you want to support even more Linux distros). As it is a lot of work, we only support one Debian at once because x86 is loosing traction on Linux distro side (for example, Ubuntu x86 is no more). – PureBasic for Linux x86 will be available on the latest Debian (at the time of writing, Debian 10). – PureBasic for Linux 圆4 will be available on the 2 last Ubuntu LTS versions (at the time of writing, it means Ubuntu 18.04 LTS and Ubuntu 20.04 LTS) Starting with PureBasic 6.00, we using the following scheme: To address this, we decided to change way we will support Linux distros. Executable created on it are no more compatible with Ubuntu 20.04 or some other recent distros.

The problem is Ubuntu 17.10 was basically only supported for 6 months and then was in support mode for a few more months. For example, the current Linux build servers are running on Ubuntu 17.10 for both 圆4 and x86 because it was the last Ubuntu version handling x86. Up to know, the Linux build servers were upgraded in somewhat chaotic manner, without real rules. and it could prevent PureBasic binaries to run at all. Every distro can have slightly different binary versions of GTK, QT, libc, zlib etc. However, as PureBasic is a closed source software, we can only ship a binary package and it can be sometimes difficult to find the right distro to run your PureBasic programs. Since 20 years, PureBasic runs natively on Linux, using seamlessly specific libraries like GTK, QT, SDL and more.
