(old)Puppy Linux Discussion Forum

Hi everyone,

Finally sucessfully compiled Cinelerra and want to share it with the world ... but can't figure how. I've made simple pets with dir2pet, but never been sucessful with new2dir. Where shall I start to read? Will I have to this very manually and very painfully?

I thought I'd throw this in the air while I go look for a solution. Thanks for all interest, I keep tabs on the "viewed" numbers you know

Battleshooter

um, what's the prob with new2dir? Are you compiling according to Barry's method?

I've had a few goes at new2dir and had no problem.

Cheers

Sorry Micko, barely provided you with anything but thin air to work on, really, worse than a newbie My excuse is I had to run dinner.

Ok, well I'm using Unnamed 1.1.

I used:
Course I was 'cd'ed to Cinelerra's folder where make, configure and etc. was. The problem is I'm sure not everything needed to run Cinelerra has been placed in the new directory. For example, the Cinelerra bin file is not in there and I can count the amount of files in there on both hands, that's way to little for a complex program like Cinelerra.

I'd like to go into more detail, but I have to rush off. More on this later. Thanks for checking in Micko.

Battleshooter

BTW, the Cinelerra program works perfectly fine. I've tested it with a video. I'm pretty certain it's compiled correctly.

The only probs I've encountered with dir2pet are trying to package python based apps, which don't seem to play well with dir2pet. Usually, with python program called xxx, I do something like:
then work backwards from that.

muggins wrote:The only probs I've encountered with dir2pet are trying to package python based apps, which don't seem to play well with dir2pet. Usually, with python program called xxx, I do something like:

Code: Select all

python install.py | cat > xxx.files

then work backwards from that.

Yes, but Cinelerra is not python based (at least that's what I thought) and I wasn't using dir2pet. I've used dir2pet with no problems before for what it's worth.

Is there some other command like the python command I can use to get make install to spit all files into one location?

I don't know if this will work or not but is worth a try . Run ./configure --help | >> configure_options.txt. This way the help output is saved in a text file. Which I find makes for easier reading and can be accessed at any time without having to run ./configure --help again.
Usually in the help it lists more in depth parameters you can pass to ./configure. What I would be trying is something along the lines of
./configure --bindir=../cinalerra/usr/bin --libdir=../cinalerra/usr/lib etc.Depending on what options are available. This hopefully would create a directory containing all the output of #make install which you can modify as required (remove the docs etc ) and then create your .pet with dir2pet.

That sounds pretty good Billwho. Thanks for that. I'll test it out and post results later.

Battleshooter

hi battleshooter,

i've also had problems with new2dir (e.g. not all files are copied if installing a lib).

My workarounds:
1. make install DESTDIR=[DIR]
you configure normal, run make and then run make install with submitting a destination-dir. this work with 'most' apps.

example: if i install faac-1.23 i run as last step if everything went well, i have all files in that dirs and subdirs. next step is to strip bins and libs and to split to packages (DEV, NLS). next is to run dir2pet

2. paco
http://www.murga-linux.com/puppy/viewtopic.php?t=34428
you configure normal, run make and then run This has worked for me with all different types of install-scripts (python..).
paco writes all installed files to its database. After installation you open gpaco (the frontend), choose the package you've installed, doubleclick, Package and than create a zipped-package of your install. Extract it to a subdirectory and there you are.

hope that helps.

aragon

Brilliant! Thanks for all the great solutions guys. Can't wait to test them, I've just gotta recompile Cinelerra again, something happened to my partition, it was wiped and I lost all my pupsaves

Shouldn't be a long time.

Hi everyone!

I'm pleased to be back to say I've recompiled Cinelerra and have made a pet of it. I chose to go by Aragon's first method and it worked a treat. Thanks for the tip Aragon, I'll probably be making most of my pets like that now.

Thanks everyone else who gave me a hand, it's really appreciated!

Battleshooter

Another thing you can do is boot a clean Puppy and create a new save file. Make as few changes as possible. Reboot so that it loads the devx_xxx.sfs file. Ignore new2dir and just compile and install the program as usual. Reboot back into your normal save-file. Now you can mount the new save-file and look around. There should be some stuff relating to the few settings Puppy had to save, along with all the files that were installed, and very little else.

It's not ideal, but it can help sometimes, and doesn't rely on third part scripts that try to figure out what's going on - if a file was added and there was enough disk-space in the savefile, it will catch it, period. It just grabs some extra junk. Comparing against a Puppy without the installed app lets you sort out which files belong to it.

Other methods are generally preferable though, since they don't require so much rebooting.

as a little addition to pizzasgood, here's how i prepare my compiling:

1. setup my actually puppy-version (as frugal on an usb-stick)
2. Boot with pfix=ram
3. Setup. nothing else!
4. Reboot. On Shutdown i create a pupsave with 512 mb and a name like compile421
5. Boot again with pfix=ram
6. Copy the new pupsave to a subdir and rename it with XXX at the beginning and the end of the name, so that it does not get picked up on bootup.
7. Copy devx to the root of the usb-stick.
8. Reboot regular
9. Compile

Whenever i need a clean pupsave for compiling, i copy the XXXpupsaveXXX beside the actual used and rename it. On next boot i can choose which one to pick up and i have a clean pupsave with no hassle. If i don't need the old one any more i simply delete it.

aragon