| |
![bachmeier's Gravatar profile Gravatar of bachmeier](//www.gravatar.com/avatar/ce63d3859c05897c939feef48d0862ad?d=identicon&s=32) | Posted by bachmeier in reply to solidstate1991 | Permalink Reply |
|
bachmeier ![bachmeier's Gravatar profile Gravatar of bachmeier](//www.gravatar.com/avatar/ce63d3859c05897c939feef48d0862ad?d=identicon&s=80)
Posted in reply to solidstate1991
| On Saturday, 8 June 2024 at 00:21:59 UTC, solidstate1991 wrote:
> On Friday, 7 June 2024 at 23:19:37 UTC, solidstate1991 wrote:
> I need to link against various system libraries, and otherwise some tools won't be able to access the D compiler unless I start them from a command line after an initialization script.
I'm using Linux Mint, it's much more stable than Ubuntu (which started to completely collapse on me for just looking the wrong way at it), but unfortunately some packages are outdated, especially the D compilers.
Okay, I installed the "curl" versions, how do I edit the activating shell scripts of DMD and LDC that they'd work as if they were installed "normally"? I don't have the time, not the capacity to test my libraries with multiple different compiler versions, and document any oddities between them (and I almost never need it thanks to D).
For Mint, I'd use the .deb and let it handle that stuff. For LDC, I have a bash alias for ldmd2 that points to the ldmd2 binary. Of course there are multiple ways to handle this, but I don't understand the point of the install script, since it leaves you without a working installation.
|