#scons — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #scons, aggregated by home.social.
-
La patrona hizo encones de queso ❤️ #scons #escones #queso #reposteria
-
La patrona hizo encones de queso ❤️ #scons #escones #queso #reposteria
-
La patrona hizo encones de queso ❤️ #scons #escones #queso #reposteria
-
La patrona hizo encones de queso ❤️ #scons #escones #queso #reposteria
-
La patrona hizo encones de queso ❤️ #scons #escones #queso #reposteria
-
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.
-
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.
-
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.
-
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.
-
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.
-
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: #datalad / :gitannex: #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 :nixos: #nix for reproducibility -
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: #datalad / :gitannex: #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 :nixos: #nix for reproducibility -
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: #datalad / :gitannex: #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 :nixos: #nix for reproducibility -
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: #datalad / :gitannex: #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 :nixos: #nix for reproducibility -
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: #datalad / :gitannex: #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 :nixos: #nix for reproducibility -
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)
-
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)
-
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)
-
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)
-
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.
-
@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.
-
@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.
-
@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.
-
@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/
-
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/
-
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/
-
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/
-
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/
-
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
It had ceased to spark joy. #autotools #scons #softwareengineering
-
It had ceased to spark joy. #autotools #scons #softwareengineering
-
It had ceased to spark joy. #autotools #scons #softwareengineering
-
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/
-
Insight of the week:
To parallelize data processing :scons: #scons, use separate scripts. scons runs Python-only builders as threads, which is amazing to keep the code simple and concise and even shared progress bars are possible, but the GIL (🤷) makes it super ineffective. Running in a multiprocessing.Process is unreliable and prone to freezing or is downright impossible when your data structures aren't pickleable.
Separate scripts means a lot more boilerplate, but at least it works.
-
Insight of the week:
To parallelize data processing :scons: #scons, use separate scripts. scons runs Python-only builders as threads, which is amazing to keep the code simple and concise and even shared progress bars are possible, but the GIL (🤷) makes it super ineffective. Running in a multiprocessing.Process is unreliable and prone to freezing or is downright impossible when your data structures aren't pickleable.
Separate scripts means a lot more boilerplate, but at least it works.
-
Insight of the week:
To parallelize data processing :scons: #scons, use separate scripts. scons runs Python-only builders as threads, which is amazing to keep the code simple and concise and even shared progress bars are possible, but the GIL (🤷) makes it super ineffective. Running in a multiprocessing.Process is unreliable and prone to freezing or is downright impossible when your data structures aren't pickleable.
Separate scripts means a lot more boilerplate, but at least it works.
-
Insight of the week:
To parallelize data processing :scons: #scons, use separate scripts. scons runs Python-only builders as threads, which is amazing to keep the code simple and concise and even shared progress bars are possible, but the GIL (🤷) makes it super ineffective. Running in a multiprocessing.Process is unreliable and prone to freezing or is downright impossible when your data structures aren't pickleable.
Separate scripts means a lot more boilerplate, but at least it works.
