| 00:07:28 | FromDiscord | <albassort> my current solution to installing the rust-dep is to tell the user to install it |
| 00:07:39 | FromDiscord | <albassort> "find the installation folder for this version and install it :) |
| 00:07:41 | FromDiscord | <albassort> (edit) ":)" => ":)"" |
| 00:08:09 | FromDiscord | <albassort> what happens if you update and forget to install the new version? Idk |
| 00:08:45 | FromDiscord | <Robyn [She/Her]> Use a define flag and the VM at compile-time to build the Rust project? |
| 00:09:13 | FromDiscord | <albassort> not everyone has cargo |
| 00:09:19 | FromDiscord | <Robyn [She/Her]> `staticExec` and also `static` blocks in general |
| 00:09:31 | FromDiscord | <Robyn [She/Her]> In reply to @albassort "not everyone has cargo": Hence define flag |
| 00:10:00 | FromDiscord | <albassort> static blocks might be the solution... |
| 00:10:15 | FromDiscord | <albassort> i wonder if i can read from stdin at compile time |
| 00:10:18 | FromDiscord | <albassort> time to find out! |
| 00:12:40 | FromDiscord | <Robyn [She/Her]> In reply to @albassort "i wonder if i": If you can't, pipe into a file and read that :) |
| 00:13:08 | FromDiscord | <Robyn [She/Her]> Even better though: Just make a Nim script you `include` in a static block if that define flag is used |
| 00:13:34 | FromDiscord | <Robyn [She/Her]> In reply to @chronos.vitaqua "https://github.com/guzba/sunny/issues/10 😔 small": It was fixed! :D |
| 00:20:59 | FromDiscord | <albassort> sent a code paste, see https://play.nim-lang.org/#pasty=sGsxvyXL |
| 00:21:04 | FromDiscord | <albassort> @Robyn [She/Her] wdyt |
| 00:21:28 | FromDiscord | <albassort> the idea is if -d:downloadNewVersion is found it'll download the correct version to the folder you're in |
| 00:21:31 | FromDiscord | <albassort> if thats possible? |
| 00:23:23 | FromDiscord | <leorize> you should consider generating a static library for your Rust stuff |
| 00:23:32 | FromDiscord | <leorize> makes it a ton easier to distribute |
| 00:26:24 | FromDiscord | <albassort> In reply to @leorize "you should consider generating": Well, i shouldn't keep it in the git so i dont see how that would help? |
| 00:26:46 | FromDiscord | <Elegantbeef> Throw it as a release then download it |
| 00:26:59 | FromDiscord | <albassort> Eh im gonna keep it on my servers |
| 00:27:08 | FromDiscord | <albassort> but that doesn't make it any easier than a dynamic lib |
| 00:27:14 | FromDiscord | <albassort> (edit) "but that doesn't make it any easier than a dynamic lib ... " added "either wya" |
| 00:27:15 | FromDiscord | <albassort> (edit) "wya" => "way" |
| 00:27:27 | FromDiscord | <Elegantbeef> It doesn't leo just dislikes dynamic libraries |
| 00:27:53 | FromDiscord | <albassort> who likes them? I'm building on Qubes which is as plain old Debian as you can get, so im not worried about it |
| 00:27:59 | FromDiscord | <albassort> (edit) "who likes them? I'm building on ... Qubesvm" added "a" | "aQubes ... which" added "vm" |
| 00:28:01 | FromDiscord | <Elegantbeef> I like them |
| 00:28:12 | FromDiscord | <albassort> Well yes beef, but you like bad things |
| 00:28:12 | FromDiscord | <Elegantbeef> Cause I'm just a contrarian |
| 00:28:21 | FromDiscord | <Elegantbeef> Have you seen your code? |
| 00:28:26 | FromDiscord | <Elegantbeef> You're not the one to shoot that shot |
| 00:28:43 | FromDiscord | <albassort> Master class in writing rust as if it were C |
| 00:28:46 | FromDiscord | <albassort> :) |
| 00:28:55 | FromDiscord | <albassort> (edit) "Master class" => "Masterclass" |
| 00:28:58 | FromDiscord | <leorize> easier to distribute for your users is what I meant |
| 00:29:01 | FromDiscord | <albassort> I am the one who codes |
| 00:30:24 | FromDiscord | <albassort> But yes, I probably will make it output static. It was static at the very start, but if you statically compile, and you change it, you need to recompile every time and also sometimes the library is cached and causes version issues |
| 01:04:27 | * | SchweinDeBurg joined #nim |
| 02:00:49 | * | SchweinDeBurg quit (Quit: WeeChat 4.4.0-dev) |
| 02:07:55 | FromDiscord | <__jont__> Making a wrapper and passing the `.a` archive file to the linker. Should I be compiling various architectures and including many different archive files to accommodate different wrapper users? ↵↵Each archive file is about 500KB, so it's not ungodly huge but I'm curious if there's a better way. I could include a few common architectures, and provide instructions for building from source |
| 02:15:26 | FromDiscord | <Elegantbeef> You could have building deps as an apart of the 'build system', but yea there are not amazingly good choices |
| 03:00:02 | * | une quit (Remote host closed the connection) |
| 03:43:15 | * | SchweinDeBurg joined #nim |
| 03:51:10 | FromDiscord | <xtrayambak> sent a code paste, see https://play.nim-lang.org/#pasty=aIWQDmeS |
| 06:36:06 | * | ntat joined #nim |
| 06:41:37 | * | PMunch joined #nim |
| 06:57:47 | * | rockcavera quit (Remote host closed the connection) |
| 07:51:47 | * | disso-peach joined #nim |
| 08:06:51 | FromDiscord | <huantian> In reply to @leorize "makes it a ton": Simply only distribute your app as a nix derivation |
| 08:06:58 | FromDiscord | <huantian> Boom dependency hell solved |
| 09:13:21 | FromDiscord | <odexine> Nix brain rot |
| 09:31:33 | * | FromDiscord quit (Remote host closed the connection) |
| 10:25:34 | NimEventer | New thread by bajith: Am I losing something by learning Nim without learning C/C++?, see https://forum.nim-lang.org/t/11853 |
| 11:21:27 | * | SchweinDeBurg quit (Quit: WeeChat 4.4.0-dev) |
| 13:44:02 | * | SchweinDeBurg joined #nim |
| 14:25:08 | * | PMunch quit (Quit: Leaving) |
| 14:29:08 | * | rockcavera joined #nim |
| 14:53:43 | * | krux02 joined #nim |
| 15:25:54 | * | xaltsc quit (Quit: WeeChat 4.3.2) |
| 15:50:38 | * | NimEventer quit (K-Lined) |
| 15:50:38 | * | NimBot quit (K-Lined) |
| 19:57:53 | * | NimBot joined #nim |
| 20:25:48 | * | NimBot quit (K-Lined) |