Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[documentation improvement] Dependencies for Artix/Arch Linux #870

Open
stamasd opened this issue Jul 27, 2024 · 7 comments
Open

[documentation improvement] Dependencies for Artix/Arch Linux #870

stamasd opened this issue Jul 27, 2024 · 7 comments

Comments

@stamasd
Copy link
Contributor

stamasd commented Jul 27, 2024

I have worked out the list of minimal dependencies that need to be installed on Artix Linux (and Arch, which is closely related). They are as follows:

pacman -S git cmake base-devel boost-libs boost libpng libjpeg-turbo
openal libogg libvorbis freeglut sdl12-compat gtk3

Note that the last one (gtk3) should be already installed if one uses a GTK-based DE, but will probably not be there for users of KDE etc. I have included it for completeness.

This was verified by me on a new install of Artix with nothing else installed except for Xorg and XFCE4.

Arch is very similar and the list of dependencies should be the same (the main difference between Arch vs Artix is the init system: systemd vs OpenRC/runit/s6/dinit - which is largely irrelevant as far as VegaStrike is concerned).

@FabioLolix
Copy link

Hello, I maintain several pkgbuilds for vegastrike on the AUR plus have a personal copy here on github for the ones I don't have on the AUR
They can all be found here https://github.com/FabioLolix/PKGBUILD-AUR_fix/tree/master/v they are all tested to build in a clean chroot with Arch's devtools

nb sdl on Arch pull sdl12-compat using only Arch repo; the old one is on the AUR

@BenjamenMeyer
Copy link
Member

@evertvorster may be able to give some insight on Arch.

@BenjamenMeyer
Copy link
Member

@FabioLolix @stamasd please feel free to add a section to https://github.com/vegastrike/Vega-Strike-Engine-Source/blob/master/script/bootstrap; we can support more in there than we necessarily provide build environments for; but that would help folks that want to do their own custom builds as it is where our build process detects the different distros and installs dependencies.

@evertvorster
Copy link
Contributor

There is a package for vegastrike-engine in the AUR, and the dependencies in the PKGBUILD is listed as:
'boost-libs' 'python' 'freeglut' 'gtk3' 'libvorbis' 'openal' 'sdl2' 'glu'

When building with that, namcap does not mention any other dependencies.

@FabioLolix
Copy link

@BenjamenMeyer I've took a quick look at function bootstrapOnArch () and bootstrapOnManjaro do you use or plan to use clang/llvm?


@stamasd

sdl12-compat

git master need sdl2

Minimal requirements on Arch are boost-libs python freeglut gtk3 libvorbis openal sdl2 glu for run plus git cmake boost base-devel for building, depends like libpng libjpeg-turbo expat and others are already depends of other pacakges installed (yet are added in my pkgbuilds for various reasons)

This was verified by me on a new install of Artix with nothing else installed except for Xorg and XFCE4.

You can test better using devtools https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot#Convenience_way

@BenjamenMeyer
Copy link
Member

I've took a quick look at function bootstrapOnArch () and bootstrapOnManjaro do you use or plan to use clang/llvm?

It doesn't matter which compiler we use. This is about installing system level dependencies so we can build at all.
Typically we use GCC on Linux (VSC on Windows); not sure off hand if others get tested too, but it wouldn't surprise me if we did. Code shouldn't be specific to a compiler.

@FabioLolix
Copy link

Code shouldn't be specific to a compiler.

Of course


Only that installing clang and llvm and then not using them is a waste, so I'll procede with removal

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants