PureBasic Forums - English

version for all the OS, including may be some new like Raspberry !

PB for Raspberry PI this is great.
But I think that before release a beta version for all platforms, need to release alpha 4 with IDE compiled in C backend to make sure there is no critical bugs.

Tremendous news!
ARM deployment is the cherry on top.

I have 75k lines with most app's, so I can live with 10-20sec compiles.
Many supporting apps and utilities are much shorter.
I'm more interested in the compiled performance after the wait.

skywalk wrote: Mon Aug 09, 2021 1:59 pm I have 75k lines with most app's, so I can live with 10-20sec compiles.

In worst case, it is back to common Tips&Tricks to reduce the compile time again (ramdrives, tracing the linking process, changing and defragmenting filesystems, changing locations, adding ram, changing hdd to sdd, using additional linker flags (precompilation!) etc to get from 20 seconds to 3 seconds again). A rather simple challenge.

I got RAM and nvme ssd drives covered.

Bitblazer wrote: Mon Aug 09, 2021 3:38 pm

skywalk wrote: Mon Aug 09, 2021 1:59 pm I have 75k lines with most app's, so I can live with 10-20sec compiles.

In worst case, it is back to common Tips&Tricks to reduce the compile time again (ramdrives, tracing the linking process, changing and defragmenting filesystems, changing locations, adding ram, changing hdd to sdd, using additional linker flags (precompilation!) etc to get from 20 seconds to 3 seconds again). A rather simple challenge.

All you need is a fast CPU. Unfortunately multithreaded compilation can not be used if I understand it right because Purebasic does not compile every single one of your include files individually but it compiles it down to one big C file. And then only one CPU core can be used. With todays cache sizes you even need not much RAM to compile a 100k lines project. And all the linked libraries are precompiled anyway. When you are working on your source code the file should be already cached in memory which means there should be no difference in SSD or HDD. Defragmentation is also a thing from the past and only important on HDDs and very old NTFS filesystems.

...or a ramdisk and awareness to save the files before shutting down.

really? Basic coders here are whinging about how long it takes for a C compiler to compile, when C programmers don't? geezus. I have a feeling the people who are whinging also aren't able to comprehend how much faster their compiled code/apps will be. Just ignore them Fred, we know you've made a BRILLIANT decision in regards to the future of PB, and I am very grateful as it empowers us all, including those who don't realise it yet - but they will

Getting closer!

I had already asked the question before

Will there be three different Purebasic libraries and compiler option for macOS later?
As I read, you can compile the programs and libraries for different architectures.

For intel: "x86_64"
For M1: "arm64"
Or: "Universal binary" for Intel and M1

With Universal, the libraries would have to be very large, as the code for Intel and M1 are included.

For Universal, I think they only need to be appended together. So two would need to be included and the universal generated from those two at compile time.

Didn't know it's so complicatwd on Linux. O only did software for Windows which basically runs for the designed version and upwards.

The text contains the phrase "What does it mean for you, PureBasic programmer ? The built-in translator of the Yandex browser translates it into Russian as "Что это значит для тебя, программист с чистой душой ?". Which is the reverse translation of DeepL "What does this mean to you, programmer with a pure soul?"

I always knew we were all programmers with pure souls here!