Question: compiling CudaText on Windows 10 (portable vs not portable and file sizes)

I’m trying to create a workflow to compile on Windows 10 by adapting cudaup.sh as a batch file instead. However, I want to fully understand how to compile it properly in the first place.

The first thing I noticed is that when I compile using lazbuild, e.g.

c:/fpcupdeluxe/lazarus/lazbuild -q --lazarusdir=c:/fpcupdeluxe/lazarus D:\GITHUB\CudaText_up-master\src\CudaText\app\cudatext.lpi

… the resulting file size is 71mb. However, the official release .exe is only around 8mb. Is this to do with some args I’m not passing to lazbuild? Or is this the difference between the cross-platform building in Linux vs Windows?

(I’m using FPC 3.2.0, Lazarus 2.3.0.)

Thanks!

[veksha]

@faulknermano, you can use cudaup.sh on windows too. just run it inside git-bash.exe

[Alexey-T]

and if you take CudaText ‘release 1.179’ then take the last ‘release’ of ATFlatControls (in the ‘releases’ page of github).