News for hackers. Stuff that matters.
Re:Homebrew 2.0.0 released by black-tea on Saturday February 02, 2019 @10:29AM (#19063456)
You get native binaries, can choose optional features and dependencies and you can easily apply your own choice of patches. That's my view as a gentoo user anyway; I don't know how much of that homebrew actually supports.
Re:Homebrew 2.0.0 released by saagarjha on Saturday February 02, 2019 @10:32AM (#19063471)
Homebrew used to support optional features, but is now moving away from this to become a binary package manager.
Re:Homebrew 2.0.0 released by h1d on Sunday February 03, 2019 @10:55AM (#19070244)
At least it should no longer take a night to compile some GUI app like back in the days.
Re:Homebrew 2.0.0 released by ninkendo on Saturday February 02, 2019 @11:36AM (#19063878)
What does “native binary” mean?
Re:Homebrew 2.0.0 released by black-tea on Sunday February 03, 2019 @03:24AM (#19068438)
Compilers like GCC can produce code specifically for your CPU such that it uses all of the special features you might have like SSE, AVX etc. When binaries are made for general use they have to be compiled with a generic feature set so might not make best use of your CPU.
Re:Homebrew 2.0.0 released by ninkendo on Sunday February 03, 2019 @06:04AM (#19068945)
So can a cross compiler, no?
Re:Homebrew 2.0.0 released by black-tea on Monday February 04, 2019 @09:15AM (#19076482)
If you know the exact flags for your CPU then you can compile for it on any other CPU using a cross compiler line GCC, yes. But that doesn't help because in practice you'll just find one binary per architecture, not per CPU.
Re:Homebrew 2.0.0 released by michaericalribo on Saturday February 02, 2019 @02:38PM (#19065139)
Compiled locally, so (posssibly) optimized for better performance than a generic binary compiled for your architecture.