This website requires JavaScript.
Explore
Help
Sign In
eUgEntOptIc44
/
gimp
Watch
1
Star
1
Fork
0
You've already forked gimp
mirror of
https://gitlab.gnome.org/GNOME/gimp.git
synced
2025-10-06 01:12:40 +02:00
Code
Issues
Releases
Activity
Files
36b660e2b22174d234808df0eea6974c94440860
gimp
/
data
/
environ
/
pygimp.env
3 lines
54 B
Bash
Raw
Normal View
History
Unescape
Escape
data: Generate .env files at build time These files has been generated by the installer scripts for historical reasons. Now that we have full-blown local builds and the upcoming MS Store version, this pervasive pratice can't continue since it creates disparity between builds.
2024-03-14 20:12:47 -03:00
__COMPAT_LAYER
=
HIGHDPIAWARE
build/windows: Debloat 'lib/python3.11' bundling After running almost all the py plug-ins, I noticed that few py modules and pkgs are used to justify the need of a slightly faster build time with .pyc. In the actual bloated status (with all .pyc), lib/python* is about 260 MB big. With the bare minimum .pyc after the tests above, python*/ is less than 90. So, let's purge the .pyc at bundling time (I'm not reinventing the wheel, Krita do this too), which reduces the .zip bundles (so the Inno and MSIX installs) in 170MB, the Installer .exe in 45MB and MSIX download in 60MB. --- Let's also disable any .pyc generation, since GIMP installed with Inno in the system-wide (aka admin) mode or installed with MSIX both doesn't handle well: py plug-ins work but have CLI errors, unlike Inno user-mode and .zip bundle.
2024-06-22 16:37:14 -03:00
PYTHONDONTWRITEBYTECODE
=
1
Copy Permalink