What is the difference between #Godot's #scons options for reducing an export template's size, and generating/using a build profile?

For example, does having `"disable_3d": true` in a build profile negate the need for `disable_3d=yes` as an scons option?

https://docs.godotengine.org/en/stable/engine_details/development/compiling/optimizing_for_size.html

https://docs.godotengine.org/en/stable/tutorials/editor/using_engine_compilation_configuration_editor.html

#GodotEngine #GameDev

Why not switch your crappy software from crappy #SCons build system to even more crappy #Bazel build system over a patch release, call it "fully backwards compatible", and then effectively leave all the distros stuck on old versions with half a dozen vulnerabilities?

Yeah, just a random reminder that #MongoDB is total crap, and you shouldn't use it. Or expect people to package it for you.

https://jira.mongodb.org/browse/SERVER-103927

#Gentoo

I want a build system that:

- is as powerful and flexible as #SCons
- as readable and concise as #SnakeMake
- has a fricking progress bar+ETA
- is  #datalad /  #gitannex agnostic (knows that files can be fetched from elsewhere
- remembers how long building things takes
- balances that to decide if rebuilding locally instead of fetching gigabytes via slow internet is favorable
- integrates well with  #nix for reproducibility

#rdm #dataAnalysis

It is beyond me why build systems like #make #scons #snakemake et al. all don't have a flag like `--pattern '*2022-*'` that will make only those files it knows how to make matching a given pattern.

(using shell brace expansion and/or globbing is risky and doesn't work fully if not all the files exist yet)

@cbleslie Yeah seems like you can set the store path globally, but that doesn't help and will cause everything to be rebuilt.

I guess theoretically each derivation *could* have its own store defined, but guaranteeing those are available might be a problem.

The way to go is probably what I currently do: pin the environment with nix, then use a build system like #scons to build the files. But then you're in build-system land again with all those quirks.

I finally finished my blog post on how to use C/C++ package managers with SCons and integrating third-party libraries into your projects. This can be useful for all Godot GDExtension users wanting to integrate a library in C++

https://paddy-exe.github.io/posts/how-to-use-scons-with-cpp-package-managers/

#godot #scons #cpp

Of course, there's a #PEP517 backend for #SCons, one of the most horrible build systems ever made by humankind.

Of course, it managed not to implement PEP517 correctly.

https://discuss.python.org/t/are-build-backends-that-use-different-keyword-arguments-to-the-standard-spec-compliant/53056
https://github.com/dholth/enscons/issues/42

#Gentoo #Python

Rzecz jasna, że jest backend #PEP517 dla Sconsa, jednego z najgorszych systemów budowania w dziejach ludzkości.

Rzecz jasna, że nie implementuje poprawnie PEP517.

https://discuss.python.org/t/are-build-backends-that-use-different-keyword-arguments-to-the-standard-spec-compliant/53056
https://github.com/dholth/enscons/issues/42

#Gentoo #Python #SCons

Are you ready to make the strategic pivot towards network effects management for a resilient supply chain?

Delve deeper:https://supplychain360.io/strategic-shift-embracing-network-effects-supply-chain-management-wordpress-article/

#SupplyChain #NetworkEffects #SCONs