ReleaseCandidat

7 ms·

31.
by ReleaseCandidat 2y ago
It depends "what" you are doing, or, more to the point, your existing knowledge. Somebody used to "low level" details (I wouldn't call it that) may find this solution simpler and faster than somebody used to contain
32.
by ReleaseCandidat 2y ago
> Debian is stable and conservative/slow in updating? Sid isn't.
33.
by ReleaseCandidat 2y ago
> must be some odd interaction between Sublime or Zed and Sequoia The same happens with MacsOS' own TextEdit. All "unknown" file suffixes are a problem
34.
by ReleaseCandidat 2y ago
For a "first" compiler? No, not at all.
35.
by ReleaseCandidat 2y ago
Temporary workaround: write nothing else but assembler source
36.
by ReleaseCandidat 2y ago
The only reason of having a Mac (sorry "real" Mac fans ;) is to be able to test your stuff with MacOS. Especially using Safari and the Iphone and Ipad simulators.
37.
by ReleaseCandidat 2y ago
Actually no. We got a `CHANGELOG` file in Git, which's last 10 lines consist of variations on `:wq`, `:x` and `:q!` :D
38.
by ReleaseCandidat 2y ago
You look up the opcodes for each assembler instructions in the ISA specifications, like https://www2.eecs.berkeley.edu/Pubs/TechRpts/2016/EECS-2016-... . Information about the machine code format starts at &qu
39.
by ReleaseCandidat 2y ago
Don't ask me. One could argue that this is the version they included in some early version and have kept for compatibility reasons, but that doesn't make(sic!) sense.
40.
by ReleaseCandidat 2y ago
If I may cite myself: Don't forget that not every Make is GNU Make, BSD and other nix like Solaris/Illumos still exist. And I'm not even talking about Windows and Nmake.
41.
by ReleaseCandidat 2y ago
If you've got your rule working for arbitrary named (i.e. not the name of the file) modules and submodules and an arbitrary number of modules and submodules generated by a single source file which uses FPP (whatever program that actual
42.
by ReleaseCandidat 2y ago
> My Makefile is portable. Oh yes, in the good old tradition of "... as long as it's some Linux on x86". [...] on Linux 2.6+ (or WSL) using GNU Make. Sorry, it's actually AMD64 _and_ ARM64!
43.
by ReleaseCandidat 2y ago
> So what's the problem exactly? They all have the samé problem: that you don't know the name (or even the number) of modules (module files) being generated without reading the source. And as a bonus every compiler uses a sligt
44.
by ReleaseCandidat 2y ago
> I've successfully written Makefiles for Fortran and they worked with ifort/ifx and gfort. Did the samé (I'm not sure if gfortran did exist at all at the time, I guess it had been g95), plus they worked with Absoft, PGI a
45.
by ReleaseCandidat 2y ago
But my argument has been that _Make_ is already too complex for the given task. And talking about complex C and C++ (to be fair, the complex ones are almost always C++ ;) projects, I would not say that CMake (or Meson or ...) is less comple
46.
by ReleaseCandidat 2y ago
> I've definitely been using .PHONY on various Linux and MacOS computers long before 2017. Me too, and I've also used Makes which didn't (on e.g. Irix). What I wanted to express had been that you can't even rely on `.
47.
by ReleaseCandidat 2y ago
Subtlety. Now the dependencies are `baz` -> `foo` -> `bar`, that is `foo` is a temporary target and won't be (re)build if `bar` already exists. Which may or may not be a problem. This temporary target (whatever the actual term is
48.
by ReleaseCandidat 2y ago
Thanks, that's it. It has been introduced with GNU Make 4.3, January 2020 https://lists.gnu.org/archive/html/info-gnu/2020-01/msg00004...
49.
by ReleaseCandidat 2y ago
I have been unclear in my formulation, sorry. The problem is a target with more than one output files, that target would look something like, which does work foo bar: baz compile $< -o foo -o bar but as this is the same
50.
by ReleaseCandidat 2y ago
Is this post for or against Make? And why is Make not a "pet project to avoid a 1 hour inconvenience that happens once every blue moon"?
51.
by ReleaseCandidat 2y ago
> Does anyone know of anything better than Make? Xmake https://xmake.io/ for C and C++ (I haven't use that for anything serious yet) and Buck 2 https://buck2.build/ if you need a really complex buil
52.
by ReleaseCandidat 2y ago
> The rest is Mac OS, which uses a BSD userland and hence BSD make by default. No. Just a really old version of GNU Make make --version GNU Make 3.81 Copyright (C) 2006
53.
by ReleaseCandidat 2y ago
That depends if the person who must do the porting knows Make or not and which GNU Make (it's always about GNU Make!) feature had been used. And chances are JS devs don't at all or just as little as the one who wrote the article.
54.
by ReleaseCandidat 2y ago
> Not true. Your dependency graph might culminate on a single final target, but nothing prevents you from adding as many targets that generate as many output files as you feel like adding and set them as dependencies of your final target
55.
by ReleaseCandidat 2y ago
And I can show you thousands of "Hello World"s that use GNU Autotools or CMake ;) But seriously: can I take a look at it (Soource + Makefile)?
56.
by ReleaseCandidat 2y ago
> He's not using C, though :-) As said elsewhere, the use-case in the article is too simple to warrant a Makefile. So: if you aren't compiling some static language, you do not need - and certainly don't want to use - Make.
57.
by ReleaseCandidat 2y ago
> neither you nor your teammates have to think about these things You're better off using a Makefile linter. But you must know about the problem before being able to solve it. And error messages like Makefile:2: *** missing sep
58.
by ReleaseCandidat 2y ago
> One of the things that makes make a great tool is how deceptively simple it is. One of the worst things of Make is how deceptively simple it looks. Make does exactly one thing: it takes input files, some dependencies and generates _exa
59.
by ReleaseCandidat 2y ago
> And why does it matter that some editors don’t know about makefiles? Because it isn't fun checking if the whitespace at the beginning of the line is a tab or spaces. And as said, you must know when to use tabs and/or spaces i
60.
by ReleaseCandidat 2y ago
Good luck writing Makefiles for Fortran, OCaml or (whenever they will really, actually work) C++ modules. There aren't many widely used build systems that can handle such dynamic dependencies without some special "magic" for

More ›