Difficult to Build Packages

Nicole4740

Hello all! I had heard about Solus before but I never really paid attention to it, untill I heard that it wasn't based off ubuntu, debian, etc. So I had to try it for myself. So far so good, but I noticed it's rather complicated to get make up and running.

I realize that they have a web page dedicated to telling users how to get it to work, but the instructions are a little vague. For example, it tells you that in order for it to work, you need to create the .solus folder (Not the hard part, I believe you just have to go to home directory and create new file) and then to create the packager file (The hard part, doesn't actually explain how to set this up. The rest of the instructions, however, are relatively simple to follow, however I don't understand why you need to do so much to get something like make up and running, especially because it is set up automatically in most Ubuntu derivatives, or at least the ones I've used.

Could someone please explain how to do the first couple of steps? If I'm unable to get it to work, this is a deal breaker because I rely on using a driver on github (https://github.com/jlam55555/veikk-linux-driver) to use my graphics tablet on Krita, and if I can't get it to work I'll have to go back to using my previous OS.

downhill

Nicole4740 I have never attempted to build a package under Solus. However, have you looked at the following:

Building a Package
About common (info at the bottom of the page)

Following is a post by Ikey in the old Solus forums that I copied into my Linux Tips database that might be useful as well.

======= Ikey Post Begin =======
Compiling Normal Things
If you're getting issues with compiling programs from source on Solus, due to missing dependencies, compiler appears broken, etc, make sure you install the development group! This is much like the build-essential package on Debian derived distributions.

sudo eopkg it -c system.devel

Compiling Kernel Things
If you're building a kernel module, you might get some "not found" errors for the kernel. You'll need system.devel as well as the headers for your kernel. Assuming you're running the LTS kernel, you'll install them like so:

sudo eopkg it linux-lts-headers

For Everything Else...
Most packages in Solus are split up into "nameOfTheThing" and "nameOfTheThing-devel". This -devel subpackage is what you actually need when you're trying to compile stuff. So for example, if a build is complaining that it cannot find x11.. you'd want libx11-devel.

When in doubt, search!

eopkg sr x11 --name | grep “\-devel”
======= Ikey Post End =======

You could also use the search function in the Solus Software Center to search for packages. Good luck!

Nicole4740

I did see the first link you posted, and that was what I was talking about when I said the initial steps were complicated. I used sudo eopkg it -c system.devel as well, because that was part of the instructions I could follow, however I'm concerned that not being able to follow the first steps is what is preventing make from working properly. I primarily just want someone to explain how to create the .solus file and the packager file like it says.

Nicole4740

Okay, I was able to figure out how to build th /.solus directory as well as how to make the packager file, however I'm unsure of where to create the common as it says , "in the same directory you will have sub-folders for packages you are building."
Does anyone know where that might be?

Justin

Nicole4740 I usually create a directory like ~/Repository and put common in there with all my packages I'm working on.

evanc

Nicole4740 what type of file is the packager file?

Nicole4740

Justin I created the Repository dirctory like you said (which is inside my home directory,) cloned the common repository into it, set up the symlinks, ran echo "include ../Makefile.common" > Makefile inside of the package I wanted to have built, and I get the error Makefile:1: ../Makefile.common: No such file or directory make: *** No rule to make target '../Makefile.common'. Stop. whenever I use make. Was I not supposed to create the Repository directory inside of my home directory as well? After all was said and one, I noticed my directory looks a little different after setting up the symlinks. It says it should look like:
| common/
| your-package/
| - Makefile
| Makefile
| Makefile.common
| Makefile.iso
But all I have is:
Makefile
Makefile.-common
Makefile.iso
(My package)

I followed all of the steps as was layed out in https://getsol.us/articles/packaging/building-a-package/en/, could anyone help me figure out what went wrong?

algent

Nicole4740 Launch terminal inside Repository folder and then run:
git clone https://dev.getsol.us/source/common.git
After this do

ln -sv common/Makefile.common .
ln -sv common/Makefile.toplevel Makefile
ln -sv common/Makefile.iso .

EbonJaeger

Just pointing out that all of this is for building a .eopkg, and not for setting up make for any random project. You can make a package of this if you really want to, but this seems to be a simple enough project that you can just use git to checkout the driver repo and following its readme and be just fine.

Nicole4740

EbonJaeger Man, I feel stupid. As soon as I got rid of the common and what not, just following the readme worked perfectly XD. Thanks for clearing that up, lol.

kyrios

evanc it is a plain text file

JoshStrobl

There isn't a "type" or extension. It's just called packager We have documentation on this... https://getsol.us/articles/packaging/building-a-package/en/