Open AlphaNERD- opened 3 months ago
The README covers the prerequisites - in that chkdeps.sh
should list like the actual stuff you need during build (libraries and generators). There kind of is an expectation that to build a C project, a C compiler/toolchain is expected but it's in the README for courtesy. :stuck_out_tongue:
Okay, i skipped over that part indeed. MX Linux must have included these tools and Void Linux didn‘t. On the other hand: Why not include it for completeness sake? This would reduce the friction we‘re currently facing while installing your whole kit.
And it really could use less friction.
The main reason they're divvied out like that is cos some stuff like bash
, coreutils
, python3
would be annoying to deal with so it made more sense to say like "you obviously need the build tools to build stuff" and then have a mapping for the libs. :thinking:
For friction my aim really is to focus on user friendly release because users shouldn't have to concern with the build. For the build process itself I think it's fine enough tho could do with more documentation written up on the Wiki for developers or anyone interested in tinkering at all.
Hello again,
So i have switched my little netbook to Void Linux because it seems to eat less RAM than MX Linux and browsing is also faster.
Of course i haven‘t given up on the XP conversion plan, so i cloned your repo and had Void install all of the depencies. Or so i thought: I installed every dependency chkdeps reported back to me, however when trying to build the packages, i still had to install make, cmake and base-devel to get the toolchain up and running.
Hence my suggestion to add the packages to the depmap file so that less technically inclined users can build the packages.