home.social

#makefiles — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #makefiles, aggregated by home.social.

fetched live
  1. @WhereTheFraserRiverFlows Thanks for sharing your experience.

    I'm either very bad at `pacman` or there's very little packaged for Arch on ARM. I'm betting it's the first one, but it could be both.

    I do know I'm well into the "submit a fix if I want a fix" corner of open source early adotpion, haha.

    I may try to build some apps I want on my Pi and see what happens when I copy them onto my PinePhone. I am pretty good to at getting things to work from source code, on ARM.

    But I guess I probably need to get a better handle on `pacman` first, to make sure I'm not duplicating someone else's efforts.

    #pinephone #linux #arch #linuxphone #devops #makefiles #armchips #ivoidwarranties

  2. @WhereTheFraserRiverFlows Thanks for sharing your experience.

    I'm either very bad at `pacman` or there's very little packaged for Arch on ARM. I'm betting it's the first one, but it could be both.

    I do know I'm well into the "submit a fix if I want a fix" corner of open source early adotpion, haha.

    I may try to build some apps I want on my Pi and see what happens when I copy them onto my PinePhone. I am pretty good to at getting things to work from source code, on ARM.

    But I guess I probably need to get a better handle on `pacman` first, to make sure I'm not duplicating someone else's efforts.

    #pinephone #linux #arch #linuxphone #devops #makefiles #armchips #ivoidwarranties

  3. @WhereTheFraserRiverFlows Thanks for sharing your experience.

    I'm either very bad at `pacman` or there's very little packaged for Arch on ARM. I'm betting it's the first one, but it could be both.

    I do know I'm well into the "submit a fix if I want a fix" corner of open source early adotpion, haha.

    I may try to build some apps I want on my Pi and see what happens when I copy them onto my PinePhone. I am pretty good to at getting things to work from source code, on ARM.

    But I guess I probably need to get a better handle on `pacman` first, to make sure I'm not duplicating someone else's efforts.

    #pinephone #linux #arch #linuxphone #devops #makefiles #armchips #ivoidwarranties

  4. @WhereTheFraserRiverFlows Thanks for sharing your experience.

    I'm either very bad at `pacman` or there's very little packaged for Arch on ARM. I'm betting it's the first one, but it could be both.

    I do know I'm well into the "submit a fix if I want a fix" corner of open source early adotpion, haha.

    I may try to build some apps I want on my Pi and see what happens when I copy them onto my PinePhone. I am pretty good to at getting things to work from source code, on ARM.

    But I guess I probably need to get a better handle on `pacman` first, to make sure I'm not duplicating someone else's efforts.

    #pinephone #linux #arch #linuxphone #devops #makefiles #armchips #ivoidwarranties

  5. @WhereTheFraserRiverFlows Thanks for sharing your experience.

    I'm either very bad at `pacman` or there's very little packaged for Arch on ARM. I'm betting it's the first one, but it could be both.

    I do know I'm well into the "submit a fix if I want a fix" corner of open source early adotpion, haha.

    I may try to build some apps I want on my Pi and see what happens when I copy them onto my PinePhone. I am pretty good to at getting things to work from source code, on ARM.

    But I guess I probably need to get a better handle on `pacman` first, to make sure I'm not duplicating someone else's efforts.

    #pinephone #linux #arch #linuxphone #devops #makefiles #armchips #ivoidwarranties

  6. Ah, the **groundbreaking** #invention of formatting Makefiles—because who needs flying cars when you've got this 🚀🙄? It's like finally inventing the wheel for chariots nobody rides anymore! Thanks for the 50-year wait, #GitHub, truly a *revolutionary* #contribution to humanity 🌟.
    github.com/EbodShojaei/bake #groundbreaking #Makefiles #revolutionary #technology #humor #HackerNews #ngated

  7. Ah, the **groundbreaking** #invention of formatting Makefiles—because who needs flying cars when you've got this 🚀🙄? It's like finally inventing the wheel for chariots nobody rides anymore! Thanks for the 50-year wait, #GitHub, truly a *revolutionary* #contribution to humanity 🌟.
    github.com/EbodShojaei/bake #groundbreaking #Makefiles #revolutionary #technology #humor #HackerNews #ngated

  8. Ah, the **groundbreaking** #invention of formatting Makefiles—because who needs flying cars when you've got this 🚀🙄? It's like finally inventing the wheel for chariots nobody rides anymore! Thanks for the 50-year wait, #GitHub, truly a *revolutionary* #contribution to humanity 🌟.
    github.com/EbodShojaei/bake #groundbreaking #Makefiles #revolutionary #technology #humor #HackerNews #ngated

  9. Ah, the **groundbreaking** #invention of formatting Makefiles—because who needs flying cars when you've got this 🚀🙄? It's like finally inventing the wheel for chariots nobody rides anymore! Thanks for the 50-year wait, #GitHub, truly a *revolutionary* #contribution to humanity 🌟.
    github.com/EbodShojaei/bake #groundbreaking #Makefiles #revolutionary #technology #humor #HackerNews #ngated

  10. Was nimmt man eigentlich heutzutage für kleinere C-Projekte als Build-System, wenn man von frickeligen #Makefiles weg will? #CMake? #Meson? #coding, #c

  11. Was nimmt man eigentlich heutzutage für kleinere C-Projekte als Build-System, wenn man von frickeligen #Makefiles weg will? #CMake? #Meson? #coding, #c

  12. Was nimmt man eigentlich heutzutage für kleinere C-Projekte als Build-System, wenn man von frickeligen #Makefiles weg will? #CMake? #Meson? #coding, #c

  13. My gosh, just when I think I've got it figured out, GNU GNoes ahead and screws me over again with some obscure syntax.

    Turns out if you want to declare a local variable in a Makefile recipe, you can't just do `var_name := value`. Oh, no. That would be too intuitive. No, you have to do it like this:

    ```
    recipe_name: var_name := value
    recipe_name:
    printf "Now I finally get to use my variable: ${var_name}"
    ```

  14. today's question: is this @ParslProject `Makefile` trying to also be a rudimentary package manager, or not?

    #Makefiles #Packaging #HowHardCouldItBe

  15. today's question: is this @ParslProject `Makefile` trying to also be a rudimentary package manager, or not?

    #Makefiles #Packaging #HowHardCouldItBe

  16. today's question: is this @ParslProject `Makefile` trying to also be a rudimentary package manager, or not?

    #Makefiles #Packaging #HowHardCouldItBe

  17. today's question: is this @ParslProject `Makefile` trying to also be a rudimentary package manager, or not?

    #Makefiles #Packaging #HowHardCouldItBe

  18. today's question: is this @ParslProject `Makefile` trying to also be a rudimentary package manager, or not?

    #Makefiles #Packaging #HowHardCouldItBe

  19. *Husband*: ...So I use a lot of #makefiles to manage building and deploying my #docker images and

    *Me, cutting him off*: sorry, _makefile_ Makefiles?

    *Husband*: yes, so

    *Me, immediately*: pervert.

  20. *Husband*: ...So I use a lot of #makefiles to manage building and deploying my #docker images and

    *Me, cutting him off*: sorry, _makefile_ Makefiles?

    *Husband*: yes, so

    *Me, immediately*: pervert.

  21. *Husband*: ...So I use a lot of #makefiles to manage building and deploying my #docker images and

    *Me, cutting him off*: sorry, _makefile_ Makefiles?

    *Husband*: yes, so

    *Me, immediately*: pervert.

  22. *Husband*: ...So I use a lot of #makefiles to manage building and deploying my #docker images and

    *Me, cutting him off*: sorry, _makefile_ Makefiles?

    *Husband*: yes, so

    *Me, immediately*: pervert.

  23. *Husband*: ...So I use a lot of #makefiles to manage building and deploying my #docker images and

    *Me, cutting him off*: sorry, _makefile_ Makefiles?

    *Husband*: yes, so

    *Me, immediately*: pervert.

  24. Can someone more experience with #makefiles than me please take a look at github.com/richfelker/musl-cro and tell me if it's possible to have a download-only step? (How?) - currently many rebuilds in Docker appear to download all the sources all over again, no matter what cache mount I try.

  25. Can someone more experience with #makefiles than me please take a look at github.com/richfelker/musl-cro and tell me if it's possible to have a download-only step? (How?) - currently many rebuilds in Docker appear to download all the sources all over again, no matter what cache mount I try.

  26. Can someone more experience with #makefiles than me please take a look at github.com/richfelker/musl-cro and tell me if it's possible to have a download-only step? (How?) - currently many rebuilds in Docker appear to download all the sources all over again, no matter what cache mount I try.

  27. Can someone more experience with #makefiles than me please take a look at github.com/richfelker/musl-cro and tell me if it's possible to have a download-only step? (How?) - currently many rebuilds in Docker appear to download all the sources all over again, no matter what cache mount I try.

  28. Can someone more experience with #makefiles than me please take a look at github.com/richfelker/musl-cro and tell me if it's possible to have a download-only step? (How?) - currently many rebuilds in Docker appear to download all the sources all over again, no matter what cache mount I try.

  29. #clang's scan-build is really awesome for simple to setup #StaticAnalysis, all you need is a compile-commands.json which is easily generated by #Meson or #CMake but also with classic #Makefiles when using bear(1). Then, just point it to the JSON and run a new build. Output is on the console as well as an HTML with a nice taint analysis which branches need to be taken for what to happen. Trade off benefit/time is real good

  30. #clang's scan-build is really awesome for simple to setup #StaticAnalysis, all you need is a compile-commands.json which is easily generated by #Meson or #CMake but also with classic #Makefiles when using bear(1). Then, just point it to the JSON and run a new build. Output is on the console as well as an HTML with a nice taint analysis which branches need to be taken for what to happen. Trade off benefit/time is real good

  31. #clang's scan-build is really awesome for simple to setup #StaticAnalysis, all you need is a compile-commands.json which is easily generated by #Meson or #CMake but also with classic #Makefiles when using bear(1). Then, just point it to the JSON and run a new build. Output is on the console as well as an HTML with a nice taint analysis which branches need to be taken for what to happen. Trade off benefit/time is real good

  32. #clang's scan-build is really awesome for simple to setup #StaticAnalysis, all you need is a compile-commands.json which is easily generated by #Meson or #CMake but also with classic #Makefiles when using bear(1). Then, just point it to the JSON and run a new build. Output is on the console as well as an HTML with a nice taint analysis which branches need to be taken for what to happen. Trade off benefit/time is real good

  33. I've been essentially nerd-sniped the last couple nights. Yesterday I couldn't stop reading the docs for GNU Make, and tonight I'm checking out Earthly. Just so interesting.

    #programming #devops #makefiles #earthly

  34. I've been essentially nerd-sniped the last couple nights. Yesterday I couldn't stop reading the docs for GNU Make, and tonight I'm checking out Earthly. Just so interesting.

  35. Okay, finally managed to look into why my #Makefiles fail with #GNU Make 4.4, what I was doing there in the first place and how to fix it

    The actual change is pretty small: github.com/xoreos/xoreos-tools

    #gnumake #build #buildsystem #floss

  36. So by default insert spaces into instead of tabs... This took me a while to figure out. Installing the official makefile plugin resolves this issue

  37. Who uses makefiles for a WebDev Workflow? Instead of #grunt or #gulp or the like?
    I consider to incorporate make in my workflow.

    #wedev #makefiles

  38. I've been struggling with #GNU #M4 these days.
    Here's my problem: I'm trying to create #docker images with configuration files dynamically. I have #makefiles to create images and a lot of environment variables that should be stored in configuration files.
    #M4 is a really old and complex templating system.
    Now I'm using #mustache templates with #chevron (:link: pypi.org/project/chevron/) that requires #python on the machine or #mo (:link: git.io/get-mo) with #bash.

    This rocks...