Been away for a while, so apologies if this has been covered already.
I came across this: https://www.ryadel.com/en/increase-memory-limit-32-bit-x86-exe-64-bit-x64-windows/
It might be helpful for compiling large/complex apps where the 32bit app address space limit (2Gb) prevents compil/build.
ONLY APPLIES to 32bit Apps runnning on 64bit Windows
A simple bit setting in the .exe header tells windows not to map 2gb of the Apps address space to the OS, effectively doubling a 32bit apps' address space to 4Gb.
This is a documented windows setting - but seems little known.
I've tried a few 32bit apps - including B4A.exe - without prooblems. I don't have any test project anywhere near needing 'large' memory though, nor the knowledge to know what other .exe's comprise the full B4A development package.
I came across this: https://www.ryadel.com/en/increase-memory-limit-32-bit-x86-exe-64-bit-x64-windows/
It might be helpful for compiling large/complex apps where the 32bit app address space limit (2Gb) prevents compil/build.
ONLY APPLIES to 32bit Apps runnning on 64bit Windows
A simple bit setting in the .exe header tells windows not to map 2gb of the Apps address space to the OS, effectively doubling a 32bit apps' address space to 4Gb.
This is a documented windows setting - but seems little known.
I've tried a few 32bit apps - including B4A.exe - without prooblems. I don't have any test project anywhere near needing 'large' memory though, nor the knowledge to know what other .exe's comprise the full B4A development package.