cd dvd blu ray burner (Pburn) 3.7.5!

[bigbass]

A light burner ported to Porteus it uses gtkdialog
for 32 bit Porteus

Major update !

This is what you need to update porteus-1.2 to the latest pburn version 3.7.5
Updated again Nov 30 2012
http://bigbass-porteus.googlecode.com/f ... _PORT2.tgz


http://bigbass-porteus.googlecode.com/f ... 1_PORT.tgz

note that pburn is no arch
meaning it will work on 64 bit or 32 bit
(remember I removed the dependencies from the package for this reason)

64bit gtkdialog for porteus 1.2
http://bigbass-porteus.googlecode.com/f ... _PORT2.tgz




all credit goes to the author of Pburn Sigmund Berglund known as "zigbert"
a nice guy and a great programmer and he was helpful in answering questions about porting his app
http://www.murga-linux.com/puppy/viewtopic.php?t=23881

you need to select a burner to get started old picture here




*I have built slackbuilds for all sources but not needed for porteus 1.2 ----32bit
if you need 64 bit sources only gtkdialog-0.8.2 would need to be recompiled for porteus-1.2


the pburn package will work on slackware 14 porteus 2 and porteus-1.2

Joe

[Hamza]

Did you written the frontend part in GTKDialog yourself ??

[bigbass]

Did you written the frontend part in GTKDialog yourself ??

No, I didnt write any of Pburn I just made it (I hope) compatible with Porteus
all credit goes to the author of Pburn Sigmund Berglund known as "zigbert"
a nice guy and a great programmer and he was helpful in answering questions about porting his app

*if anyone has issues I will forward the error logs to him so he could maintain
his app more linux friendly

Joe

[Hamza]

Thanks for info

[brokenman]

As usual bigbass ... excellent stuff. keep em coming. I will be using k3b for next release as it has a little more fucntionality, but i am not 100% happy with it as it refuses to rip individual video titles. I will see what users think but perhaps we could swap it out for favour of pburn and a seperate media ripper.

[Hamza]

I am wondering if Pburn does not mean "Porteus Burn"... 8)

[Ahau]

Hi bigbass,

On my machine, pburn does not work out of the box-- it fails to find the device and burn to it once you select an action. I believe beny had this behavior too. I tracked it down and found that the cdrecord option wasn't giving full instructions -- it was trying to burn to 'sr0' instead of 'dev/sr0', the actual device. I went to /dev/ and saw that /dev/cdrom is symlinked to -> sr0, not /dev/sr0 (maybe a difference between porteus and puppy, or parent distros).

Anyway, I resolved this with some minor modification to /usr/local/pburn/func_build_command: I changed:

Code: Select all

TMP=`readlink $INDRIVE`; [ "$TMP" ] && INDRIVE=$TMP #/dev/cdrom is a link to the actual driver
TMP=`readlink $BURNDEV`; [ "$TMP" ] && BURNDEV=$TMP

to:

Code: Select all

TMP=`readlink -f $INDRIVE`; [ "$TMP" ] && INDRIVE=$TMP #/dev/cdrom is a link to the actual driver
TMP=`readlink -f $BURNDEV`; [ "$TMP" ] && BURNDEV=$TMP

and it works. I'm including this in my XFCE build for next release. Please check with the author and see if this change would mess things up on his end, in puppy. I'm hesitant to make this change on my own

Also, please check if vamps is truly needed for DVD capabilities...that project is 6 years old, there must be some other way? Maybe it's already implemented and vamps is just an option?

Thanks!

[bigbass]

Ahau

it was trying to burn to 'sr0' instead of 'dev/sr0', the actual device. I went to /dev/ and saw that /dev/cdrom is symlinked to -> sr0, not /dev/sr0 (maybe a difference between porteus and puppy, or parent distros).

good catch those small gotchas are hard to find

thanks I will pass on the info
rev 1 # readlink -f used for Porteus by Ahau Feb-18-2012
I added the fix to the package

bumped updated again


Joe

[bigbass]

updated first post

Posted after 2 days 6 hours 57 minutes 45 seconds:
updated to 3.5.0

[Ahau]

bigbass, this is great, the latest version opens incredibly fast

However, installing it on my system in always fresh mode, it again throws an error window at startup, asking for /root/my-documents/tmp folder -- did you just add that directory to the previous version of the slack package, or did you add something to pburn that created the tmp folder if it didn't exist already?

[Hamza]

Code: Select all

[ ! -d "/root/my-documents/tmp" ] && mkdir -p /root/my-documents/tmp

[bigbass]

I cant compile 64 bit on my box so here are some tools to get the job done




cddetect
If you have problems compiling cddetect or cddetect_quick, include a header. Add this to cddetect.c

Code: Select all

#include <limits.h>

close
If you have to compile dvd+rw-tools-7.1 close.cpp, and it gives an error, you should add this line to transport.hxx

Code: Select all

#include <limits.h>

and compile with this

Code: Select all

g++ -o close close.cpp

vamps.SlackBuild will also compile 64bit

Code: Select all

#!/bin/sh
# Heavily based on the Slackware 13.0 SlackBuild
# http://vamps.sourceforge.net/
# Packager Vincenzi Loris - [email protected]
# fix  prefix directory for build and remove the strip command added by bigbass
# this avoids the need for a patch
# Exit on most errors
set -e

CWD=`pwd`
TMP=${TMP:-/tmp/tgz}
PKG=$TMP/package/vamps
NAME=vamps
VERSION=0.99.2
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
	i?86) ARCH=i486 ;;
	arm*) ARCH=arm ;;
	*) ARCH=$( uname -m ) ;;
  esac
fi
BUILD=4sl
SOURCE=http://downloads.sourceforge.net/project/vamps/Vamps/$VERSION/$NAME-$VERSION.tar.gz?use_mirror=garr

if [ ! -e $NAME-$VERSION.tar.gz ]; then
wget -c $SOURCE
fi


if [ ! -d $TMP ]; then
mkdir -p $TMP
fi
if [ ! -d $PKG ]; then
mkdir -p $PKG
fi

cd $TMP
tar xzvf $CWD/$NAME-$VERSION.tar.gz
cd $NAME-$VERSION
chown -R root:root .

if [ "$ARCH" = "i486" ]; then
  sed -i "s|-O3|-Os -fPIC -fomit-frame-pointer -pipe -march=i486 -mtune=i686|g" vamps/Makefile
elif [ "$ARCH" = "x86_64" ]; then
  sed -i "s|-O3|-Os -fPIC -fomit-frame-pointer -pipe|g" vamps/Makefile
fi

# fix  prefix directory for build and remove the strip command added by bigbass
# this avoids the need for a patch
sed -i 's/\/usr\/local/\/usr/' vamps/Makefile
sed -i 's/LDFLAGS/\#LDFLAGS/' vamps/Makefile
sed -i 's/\/usr\/local/\/usr/' play_cell/Makefile
sed -i 's/LDFLAGS/\#LDFLAGS/' play_cell/Makefile


make
mkdir -p $PKG/usr/bin
cp vamps/vamps $PKG/usr/bin
cp play_cell/play_cell $PKG/usr/bin
mkdir -p $PKG/usr/doc/$NAME-$VERSION
cp -a COPYING INSTALL $PKG/usr/doc/$NAME-$VERSION
cd $PKG
find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
cat $CWD/slack-desc > $PKG/usr/doc/$NAME-$VERSION/slack-desc
cat $CWD/$NAME.SlackBuild > $PKG/usr/doc/$NAME-$VERSION/$NAME.SlackBuild
ADD=$(ls /var/log/packages/ | sed -ne 's/\(libdvdcss\)-\([^-]\+-[^-]\+-[^-]\+\)/\1 >= \2/p') \
#requiredbuilder -v -y -s $CWD $PKG
makepkg -l y -c n $CWD/$NAME-$VERSION-$ARCH-$BUILD.txz

if [ "$1" = "--cleanup" ]; then
rm -rf $TMP
fi

[Ahau]

thanks, bigbass!

64-bit comes with dvd+rw-tools by default, but I don't see a file called "close"... I downloaded the source and don't see close.cpp there, either. Do you have a link to the source you're using?

Also, I found a link to the source for cddetect_quick (packaged with hotplug2stdout). It has a 32-bit binary for cddetect_quick and a .c file for cddetect. I was able to get cddetect to compile in 64-bit with the header you mentioned, but don't see a .c or .cpp file for cddetect_quick... any suggestions, or are these files interchangeable?

[Hamza]

It's not an app written entirely in script language like python or shell ?

[bigbass]

Hey Ahau
I will updated the other post later but this answers the new questions you asked


main page dvd+rw-tools-7.1
http://fy.chalmers.se/~appro/linux/DVD+RW/

sources dvd+rw-tools-7.1
http://files.myopera.com/jpline/blog/dv ... .1.tar.bz2
close.cpp is there but it is not included in the makefile so I manually compiled it it is a plug-in dependency only ( not sure yet when its used in the code I have to read over it a bit)
----------------------------------------------------------------------------------------------------------------------





official hotplug2stdout
http://www.bellut.net/projects.html


unofficial modified hotplug2stdout-1.2.1 used in Pburn just cddectect_quick

look in the sources cddetect for this line to see which is original and which is modified
* Cut down for fast detection if disc inserted only. BK may 2008

Code: Select all

wget --user=puppy --password=linux http://bkhome.org/sources/alphabetical/h/hotplug2stdout-1.2.1.tar.gz

then you compile with this you will see now where the cddetect comes from
dont feel bad it was undocumented a four year old hack I had to sort though the ashes too

add this to cddetect.c

Code: Select all

#include <limits.h>

Code: Select all

 gcc -o cddetect_quick cddetect.c
 strip --strip-unneeded cddetect_quick