./configure: No such file or directory when building .pet

[trawglodyte]

My first try at building a .pet from a .tar.gz and I'm stuck at step 1.

You can see in the terminal I'm in the right directory from output of ls -l. I also have SFS-Load on-the-fly showing I have devx loaded if that is needed.

I tried this on another .tar.gz for OBS_24.0.3 and it gave me the same message.

Code: Select all

bash: ./configure: No such file or directory

I did rename the file and extracted folder, that wouldn't be the problem would it?

[mikewalsh]

@trawglodyte :-

I've come across this before myself. Upon closer inspection, you don't look to HAVE a 'configure' file present.......and not all build-systems work like this anyway.

There's a huge choice of build-automation stuff out there:-

https://en.wikipedia.org/wiki/List_of_b ... n_software

Most of them I've never heard of, but I have seen Ninja, Meson and even Ansible mentioned before on the forum. Make is, of course the most common one in general use this side of the fence, though 'autoconf' tends to be used more & more often with this nowadays.

I'm not sure about this. General Puppy guidelines on this sort of stuff tend to be a bit out-of-date now. What does it say in the 'ReadMe' and 'Install' files? They ARE generally there for a reason, and often provide vital clues as to why something may not be working.....

Don't get discouraged. Compiling seems to be summat of an 'art-form'; some people take to it like a duck to water, but for many, they never CAN make it work. I fall into the latter category; it only ever succeeds for me with relatively simple stuff, usually where the "build-recipe" is clearly given beforehand.....

(shrug...)

Mike.

[trawglodyte]

@mikewalsh

That's what I needed to know. I thought there should be a "configure" in the folder. I just found several instructions for making a .pet and they all had ./configure for the first thing. Any way to make a .pet from .tar.gz's without a configure?

The README linked me to stuff that seemed like Debian/Ubuntu instructions. I can try it, but not sure if the commands work in my FossaPup terminal.

Oh, I do have cmake. So I can try that to compile it in FossaPup64_9.5?

[Jasper]

@trawglodyte

Looking at your source files, you will need Cmake to compile the application.

First, create a "build" directory.

If you want a GUI for Cmake, it is included in my DevX

https://www.mediafire.com/file/elq7ijit ... 5.sfs/file

or if just want the application "as is"

cmake-3.28.1-x86_64
https://www.mediafire.com/file/9jtrb6v7 ... 4.pet/file

[mikewalsh]

@mikewalsh

That's what I needed to know. I thought there should be a "configure" in the folder. I just found several instructions for making a .pet and they all had ./configure for the first thing. Any way to make a .pet from .tar.gz's without a configure?

The README linked me to stuff that seemed like Debian/Ubuntu instructions. I can try it, but not sure if the commands work in my FossaPup terminal.

Oh, I do have cmake. So I can try that to compile it in FossaPup64_9.5?

@trawglodyte :-

Pass!

Seriously, I am NOT the best person to ask about this. My compiling skills are atrocious; there are other Puppians who can advise you FAR better. Primarily, I'm a "packager".....or more to the point, a"re-packager". I'm good at taking existing packages, then tweaking or modifying them to work under Puppy. Where I've created/built various utilities from scratch, they're almost always script-based, and make use of existing functions that are already in Puppy to start with.

All I can say is, do some more research. Ask questions in the 'Programming' section; you may get more joy there. And......good luck! (At least I'm trying to be honest here..!)

Mike.

[trawglodyte]

If you want a GUI for Cmake, it is included in my DevX

https://www.mediafire.com/file/elq7ijit ... 5.sfs/file

or if just want the application "as is"

cmake-3.28.1-x86_64
https://www.mediafire.com/file/9jtrb6v7 ... 4.pet/file

Perfect! yah, I was just trying here and it wasn't happy with the cmake 3.16 I have. I like terminal for stuff like this. It makes me feel like a badass even though I'm actually just copying and pasting instructions I find online.

[Jasper]

The above Pet file does provide a QT GUI and it is simple to use.

If you do run into errors in the "Build" directory you created there will be a text file with a list of errors.

If you want a CLI build only:

cmake-3.27.8
https://www.mediafire.com/file/g2q0coo2 ... 4.pet/file