#autotools

[ryfoxbread]

cow tools reminds me of autotools. and then i get sad

[leav3z]

Makefile is a simple build system, handling the dependency, and caching, of each TARGET. The target is a abstracted, generic item.

[taevisionceo]

TAEVision 3D Mechanical Design Tools GarageTools Repair RepairTools RemovalTools RemovalGlowPlugs glowplugs M8x1 MercedesBenz CDI V6 OM642 (2,8L + 3,2L) Ref. 6041640C... �� TAEVision Engineering on Pinterest ▸ TAEVision Engineering on Google Photos

Data 243 - May 17, 2023

[precisebuilt]

#didyouknow #precisebuilt #torquewrench #torquetospec #torquing #lugnuts #fasteners #autotools #tools #toolsforthejob #facts https://www.instagram.com/p/CnhfeYKp6t5/?igshid=NGJjMDIxMWI=

[cinnamonwolfy]

i have some criticisms for the gnu project

like, a lot of criticisms. there's so many things they do so wrong and are so questionable, it's not even funny. then again, stallman still is part of the foundation, and stallmanisn is suuuper contagious (even i had it for a bit, luckily @raisinware was there to deradicalize me before it was too late <3 <3 <3)

i have a lot to say, but i will just put the top 3 things wrong with gnu and the fsf in this post

so let's start with one of the lesser ones, lgpl. in theory, lgpl should be a lot less restrictive and easier for companies to follow without being forced to open-source their code (i know that for a lot of foss devs that this is a hard pill to swallow, but some software is best left to be closed-source. not everything needs to be foss, and for most commercial software projects, it would be detrimental to have such stuff open-source). well, the lgpl is just the gpl with a shared linking exception, basically making it kinda useless. the lgpl really should've been a stricter mpl-like license. mpl just makes more sense for libraries than gpl does, and making lgpl almost fully compatible with mpl would've helped a lot with mpl-gpl interop. sadly, lgpl is still gpl for the most part, which means that barely anyone uses it (at least compared to gpl)

one of the bigger gripes i have with the gnu project is autotools. i'm not gonna sugarcoat it, autotools is garbage. it generates so much stuff that goes unused due to it being legacy cruft from other proprietary unix clones, and it's a biggger pain in the rear than cmake to set up a project with it and actually make it compile something. i guess it works nicely for compiling software on legacy unix systems, but gnu is not really legacy, as it keeps getting updated. and with how many gnu extensions they already do with their software to the point where there's software that depends on gcc to compile at all, you would assume that they would get rid of all of the legacy cruft that nobody really uses anymore (unless you're runinng it on aix, in which case, you'd go with an older version anyway). this is why a lot of my projects use their own custom autotools-like build system alongside meson, so that way i can accomplish cross-platform compilation while also supporting old unix systems via the posix shell scripts

and now, my biggest problem with gnu: their complete obsession over c90, despite c99 existing and being hundreds of time better (and that's before you consider c11, which is already out of date, and rust). gnu still believes that current year is 1991, and thus still uses c89/c90 in a lot of their projects (which is why their projects are so messy), even projects such as gnulib, which even though it already requires c99, they still write a lot of the library in c90 and even deliberately just avoid using c99 for no reason known to science. i swear, they act like rust programmers do, but instead of a nice and modern language that deserves that attention, it's an ancient piece of crap that nobody except them likes using, that has been replaced by newer versions of the c language and even rust

anyways, that's enough complaining for one post (i did just write a nyt bestselling book above x3). it was nice to release some of the stuff i've had to deal with while creating and maintaining portalinux with my gf. i have more stuff about gnu and the fsf to complain about, but that would be too long, even for tumblr standards x3. so i will probably end up making a video of it on my yt channel whenever i feel comfortable enough with my voice to post :3. if you made it this far, thank you for putting up with so much text, i just really needed to let some steam off :3

i wish you all a good day (or night) :3

[blubberquark]

Nothing encapsulates my misgivings with Docker as much as this recent story. I wanted to deploy a PyGame-CE game as a static executable, and that means compiling CPython and PyGame statically, and then linking the two together. To compile PyGame statically, I need to statically link it to SDL2, but because of SDL2 special features, the SDL2 code can be replaced with a different version at runtime.

I tried, and failed, to do this. I could compile a certain version of CPython, but some of the dependencies of the latest CPython gave me trouble. I could compile PyGame with a simple makefile, but it was more difficult with meson.

Instead of doing this by hand, I started to write a Dockerfile. It's just too easy to get this wrong otherwise, or at least not get it right in a reproducible fashion. Although everything I was doing was just statically compiled, and it should all have worked with a shell script, it didn't work with a shell script in practice, because cmake, meson, and autotools all leak bits and pieces of my host system into the final product. Some things, like libGL, should never be linked into or distributed with my executable.

I also thought that, if I was already working with static compilation, I could just link PyGame-CE against cosmopolitan libc, and have the SDL2 pieces replaced with a dynamically linked libSDL2 for the target platform.

I ran into some trouble. I asked for help online.

The first answer I got was "You should just use PyInstaller for deployment"

The second answer was "You should use Docker for application deployment. Just start with

FROM python:3.11

and go from there"

The others agreed. I couldn't get through to them.

It's the perfect example of Docker users seeing Docker as the solution for everything, even when I was already using Docker (actually Podman).

I think in the long run, Docker has already caused, and will continue to cause, these problems:

Over-reliance on containerisation is slowly making build processes, dependencies, and deployment more brittle than necessary, because it still works in Docker

Over-reliance on containerisation is making the actual build process outside of a container or even in a container based on a different image more painful, as well as multi-stage build processes when dependencies want to be built in their own containers

Container specifications usually don't even take advantage of a known static build environment, for example by hard-coding a makefile, negating the savings in complexity

[niconiconwo]

I've decided on learning CMake so I can get things to build on Win10. I realised being stubborn about it was actually stupid as hell, so now I gotta figure this shit out.

The saving grace is CMake is cross platform, so I can use it to generate either Unix make or NMake files. And granted, once I start working with source trees that are actually complicated it'll be useful to have an autotool that can do configuration for me.

[hydralisk98]

Content data to study

Tcl, Fish, KDE Plasma 5.27+, RC, ES, RIO, ACME, Kwin, Liquidshell, Plasmoids, OpenDylan, SimH PDP8, ChrysaLisp, ZealOS' DolDocs, Haiku, NetBSD, Plan9, Smalltalk, Steel Bank Common Lisp, Common Lisp Object System, NetLogo, TROPIX, PhantomOS, ITS, CP/M, DOS, Unix v6-v7, Oberron A2 Bluebottle, ObjectREXX, DEC Alpha, GNU Hurd, MINIX3, Tcl alone, TclX, Tcl/Tk, PAL for PDP8, DIBOL, Synergy DBL, GAS, SVG, TextWorld, AROS, TakeCommandConsole, Krita with G'MIC, Blender, Inkscape, Falkon, Konqueror, LibreWolf, Lemon, Tlick, nsCDE, Turbochannel / Alpha AXP, GRUB, Paradise, Parade, Uxn, Tmux, OpenSSH, POSIX, Hypervisor, KVM, OpenBSD Sandbox / Jails, Git, GNU Bazaar, UTF-8, Microdot Linux, BeagleV-Fire, BeagleboneY-AI, DECmate II+, DECmate III with its dedicated disk drive unit, DEC Alpha, DUNNET, Emacs, Vim, Vi, VimWiki, Org-Mode, Zork, A Mind Forever Voyaging, Evennia, LambdaMOO, , Rust, ALGOL68, Grulx, Frotz, Z-Machine, Dolphin, Midnight Commander, GNU Taler, GDB, BinUtils, Autotools, Coreutils, Linux-libre, GNU Jami, GNUnet, MediaGoblin, Goblin Tools, LilyPond;

Super Cluedo, Die Macher, Century Spice Road, Century A New World, Carcasonne, Werewolves Pact Edition, Talespinner EU, D&D 5E, Pathfinder 2E, Cyberpunk RED, GilaRPGs' NOVA, Mark Rosenfelder, Ken Silverman, Nicky Case, Yukari Hafner, Prosperity ruleset for Landlords Game, Diplomacy, HAM Radio, RTTY, Hard-Copy terminals, interactive video terminals / lightweight clients, tabulators, typewriters, unit record equipment, cardboard counters, printing presses, phonebooks, yellow pages, pen & paper games, gamebooks, zines, atlases, road maps...

[layingeggs]

Why do people online say that photoshop is better than gimp and gimp is unusable? I saw one post saying that gimp has no circle autotool and that it takes half a dozen steps to draw a circle.

But like, setting the brush size to 500 and drawing a black dot, and then setting the bush size a few points lower and drawing a slightly smaller white dot inside the black dot. That's less than 60 seconds?

I donno, is it literally just a case of 'autotooling a circle is one click but drawing two dots is two clicks plus adjusting brush size'? Is it just a matter of the time adding up long term so that extra hours of your life are taken up with doing things that should rightly have been automated?

Like, that's bad, but it's not end of the world. I don't get it.

[hackernewsrobot]

Autodafe: Tools for freeing your project from the clammy grip of autotools

https://gitlab.com/esr/autodafe

[viktec]

VT18692 Crankshaft pulley assembly-for FORD 1.0#autotools #autorepair .Specially designed to remove and install the crankshaft pulley, in order to replace the timing belt. .Applicable: FORD 1.0L Ecoboost engine. .FM number: 303-1611, 303-1611-01, 303-1611-02. .Includes a torque multiplier. .Max torque: input-300Nm, output-1,500Nm. .Gear ratio: 1:5, input drive: 1/2, output: 3/4. Visit our website: www.chianviktec.com to get more.

[leav3z]

The execution of Configure script actually needs other auxiliary files. The autoconf branch only define how to check the environment. There's another branch define the real build configurations. A file called Makefile.am is composed manually, defining the the binary target, the source files, link flags and others. Automake tool will utilize the Makefile.am generate a Makefile.in file and others, which will be used by the Configure script to generate the real makefile

[taevisionceo]

TAEVision 3D Mechanical Design Tools GarageTools Repair RepairTools RemovalTools RemovalGlowPlugs glowplugs M12x1.25 MercedesBenz CDI Engines (OM604 - 0M605 - OM606)... Ref. 1260000... ▸ TAEVision Engineering on Pinterest ▸ TAEVision Engineering on Google Photos

Data 238 - May 17, 2023

[offershub07]

#FLORISCA #AutoTools #JackRatchetWrench #LaborSaving #TireWheelJack #CarMaintenance #TravelEssential #AutoAccessories #EasyCarLift #MechanicTools#TechSolutions #GadgetGuru #InnovationNation #ProblemSolved #TechTips #GadgetWizard #SmartTech #DIYTech #InnovativeIdeas #TechHacks #FutureTech #DigitalSolutions #EcoTech #GadgetLife #SmartLiving #InventiveIdeas #TechEnthusiast #ProblemSolver #CreativeSolutions #InnovationInspiration #GadgetGeek #DIYInnovation #TechInnovations #CuttingEdgeTech

[xhorseshop]

🚗 Introducing OBDSTAR ODO Master - Odometer Adjustment and Car Maintenance! 🚀

Highlights: OBDII Support 🚗 Data Backup & Recovery 💾 Odometer Reading, Writing & Reset 🛣️ Oil Service Reset 🛢️ DTC Reading & Clearing ❗ One-Click Upgrade 🔝 Airbag Reset Function 💨 Instruction Documents 📖 Wide Vehicle Coverage 🚘 New Help Function ❓

Get yours now! 👉

OBDSTAR #ODOmaster #OdometerAdjustment #CarMaintenance #CarTech #AutoTools