Compile Question

[SomeDudeInAZ]

Hi Folks,

In order for me to make the fulltime switch over to OM there are a few programs that I’ll be needing that aren’t in the repo.

While flatpacks and appimages can fill in for some things, I find that even when they are available I wind up compiling anyway after a “trial run”.

Before I go down that particular bunny trail I figured I’d check and see if there were any specific OM related libraries I needed.

For instance over on Mint (my current DD) “build-essential” is a required package.

I see that checkinstall is in the repo

Or can I just compile my happy little head off

Thanks

Ref: https://forums.linuxmint.com/viewtopic.php?t=230142

[zeroability]

@SomeDudeInAZ

For instance over on Mint (my current DD) “build-essential” is a required package.

I don’t know what a DD is, but we have a package that basically does what you are asking:

https://openmandriva.pkgs.org/cooker/openmandriva-main-release-x86_64/basesystem-build-4-31-omv2390.x86_64.rpm.html

It should include just about everything you would need to build something in OMLx.

sudo dnf in basesystem-build

We also have packaging tools if you decide you want to share your work with others.

[vannax (Mike)]

I believe DD is “Daily Driver.”

[rugyada]

@SomeDudeInAZ

For instance over on Mint (my current DD) “build-essential” is a required package

Forum Search

[SomeDudeInAZ]

::sigh:: you know, I ran that search and nothing came up.

It’s been that kinda day.

Thank you.

[WeirdGnome]

Could you share more about those packaging tools? I’m going be in a need to build some packages and will be more than happy to share with others.

[sez11a (Rich Sezov)]

Maybe this will help?

How to Build and Submit Packages for OpenMandriva

Making Packages You must have packaging tools installed: sudo dnf install packaging-tools These tools give you templates for spec files and tools for building RPMs. You’ll start with the various v* tools: vs: vs stands for vi specfile. By default it opens a specfile template in Vim, but it respects the $EDITOR and $VISUAL environment variables. vl: vl is vs for libraries. It loads a different template. vp: vp is vs for Python modules. It loads a different template. vpl: vpl is vs for Perl …

[zeroability]

You typically want the previously mentioned package, rpmdevtools and packaging-tools. If you want to develop with the kernel (or any other library) you’ll need the respective devel package.