#scons — Public Fediverse posts

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.

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

#Gentoo

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

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

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

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: #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

#rdm #dataAnalysis

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

#rdm #dataAnalysis

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

#rdm #dataAnalysis

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

#rdm #dataAnalysis

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

#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)

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)

Today's progress on #FreeBSD #Linuxulator "userland from source" project: We have build systems! 🥳

Supported now (apart of plain #make): GNU #autotools (including #autoreconf), #cmake, #meson and #ninja!

They're all supported with their original #ports "USES", by some #bmake trickery in my new "USES=linuxsrc", fixing up just the parts that are different when building from/for the Linuxulator (like adjusting dependencies and commands to use the #Linux-native versions).

Ok, no #scons yet, didn't need it so far 🙈

I have just updated and tagged GDExtensionTemplate for Godot 4.2!

If you want to use an existing C++ library in #Godot or use #CMake instead of #Scons for your C++ extension, check it out!

https://github.com/asmaloney/GDExtensionTemplate

It takes care of all the setup/building/linking with godot-cpp and the GitHub CI so you can focus on your code right away.

#GodotEngine #Godot4 #GDExtension #extension #plugin #GameDev #IndieDev #cpp

I have just updated and tagged GDExtensionTemplate for Godot 4.1!

If you want to use an existing C++ library in #Godot or use #CMake instead of #Scons for your C++ extension, check it out!

https://github.com/asmaloney/GDExtensionTemplate

It takes care of all the setup/building/linking with godot-cpp and the GitHub CI so you can focus on your code right away.

#GodotEngine #Godot4 #GDExtension #extension #plugin #GameDev #IndieDev #cpp

Welp, I tried to get #distcc working with #scons, but it never seemed to pick it up. I guess I'll have to try another day.

@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/

#godot #scons #cpp

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

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

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

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

anyone know about #scons and specifically #godot? is there a way to tell it to have a separate build directory so the object files from each platform don't overwrite each other?

anyone know about #scons and specifically #godot? is there a way to tell it to have a separate build directory so the object files from each platform don't overwrite each other?

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

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

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

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

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

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

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