29 Apr
2011
29 Apr
'11
10:59 p.m.
Tim,
I apologize for the delays, life seems to have caught up with me recently. This week and
the following are finals for the semester so I am under a great stress and large workload.
I also have not been able to successfully install Trinity either on Arch Linux. Baho and
David haven't grasped the concept of portability so I don't have it working.
Again Sorry,
Calvin Morrison.
Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote:
Hi Serghei, Calvin,
Can you two please update me on the CMake status of kdegraphics? I would
like to keep things moving if possible; I know Calvin has on the Etherpad
that he is waiting for some kind of macro from Serghei; if this could be
coordinated and fixed I would appreciate it.
Once kdegraphics is complete I will initate TQt4 conversion and autobuilds
on this end.
Thanks!
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
30 Apr
30 Apr
12:11 a.m.
New subject: [trinity-devel] kdegraphics CMake Status
Serghei,
Do you think you can wrap up kdegraphics by yourself? AFAIK there are
only a couple modules within kdegraphics left.
Tim
Tim,
I apologize for the delays, life seems to have caught up with me recently.
This week and the following are finals for the semester so I am under a
great stress and large workload. I also have not been able to successfully
install Trinity either on Arch Linux. Baho and David haven't grasped the
concept of portability so I don't have it working.
Again Sorry,
Calvin Morrison.
Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote:
Hi Serghei, Calvin,
Can you two please update me on the CMake status of kdegraphics? I would
like to keep things moving if possible; I know Calvin has on the Etherpad
that he is waiting for some kind of macro from Serghei; if this could be
coordinated and fixed I would appreciate it.
Once kdegraphics is complete I will initate TQt4 conversion and
autobuilds
on this end.
Thanks!
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
1:02 a.m.
New subject: [trinity-devel] kdegraphics CMake Status
On Saturday 30 April 2011 03:11:22 Timothy Pearson wrote:
Serghei,
Do you think you can wrap up kdegraphics by yourself? AFAIK there are
only a couple modules within kdegraphics left.
I will try, but this will take some time, because I will be pretty busy next
weeks/months.
Calvin, send me you current work on kdegraphics, i will try review it and to
commit it to svn.
--
Serghei
1:44 a.m.
New subject: [trinity-devel] kdegraphics CMake Status
On 04/29/2011 06:59 PM, Calvin Morrison wrote:
Tim,
I apologize for the delays, life seems to have caught up with me recently. This week and
the following are finals for the semester so I am under a great stress and large workload.
I also have not been able to successfully install Trinity either on Arch Linux. Baho and
David haven't grasped the concept of portability so I don't have it working.
Don't understand the
"Baho and David haven't grasped the concept of portability so I don't have it
working."
The Build system i have (the Makefile and the bash script) was designed to build trinity
from a constantly changing svn.
If you use the entire build system to create the binary packages it will work and create a
installable TDE.
It is what I am currently using now.
I installed a clean i686 arch install added wireless, alsa, xorg and the dev tools. Then
built and installed trinity.
It is not complete but provides a usable TDE.
I am waiting for the cmake port to finish.
When trinity releases 3.5.13 as complete I will have the PKBUILD scripts use the source
tarballs to build it entirely as what is done currently in Arch.
Until that happens I am stuck with the system I have.
Again Sorry,
Calvin Morrison.
3:58 a.m.
New subject: [trinity-devel] kdegraphics CMake Status
"Baho and David haven't grasped the concept of portability so I don't have
it working."
The Build system i have (the Makefile and the bash script) was designed to
build trinity from a constantly changing svn.
If you use the entire build system to create the binary packages it will
work and create a installable TDE.
It is what I am currently using now.
I installed a clean i686 arch install added wireless, alsa, xorg and the dev
tools. Then built and installed trinity.
It is not complete but provides a usable TDE.
I am waiting for the cmake port to finish.
When trinity releases 3.5.13 as complete I will have the PKBUILD scripts use
the source tarballs to build it entirely as what is done currently in Arch.
Baho, No I understand,
Using SVN is actually fine, I prefer it and need to use the svn repos.
I was referring to the Make file and build scripts. basically
following the PKGBUILD guidelines and rules, you should be able to
just run makepkg and it should work, without any other script. I
understand you like to automate it, have a chroot and such, etc. but
all the packages should be independant of any system of automation.
Serghai,
Yes I'll tar up what I have currently and send it over to you immediately.
Sorry I haven't made progress,
Calvin Morrison
3:59 a.m.
New subject: [trinity-devel] kdegraphics CMake Status
Also Baho,
you don't seem to have included mkarchchroot, so i can't even use your system.
Calvin Morrison
10:48 a.m.
New subject: [trinity-devel] kdegraphics CMake Status
On 04/29/2011 11:59 PM, Calvin Morrison wrote:
Also Baho,
you don't seem to have included mkarchchroot, so i can't even use your system.
Calvin Morrison
by running make in the scripts directory gives you the instructions for
using the system.
All that is needed is to
add the user to sudo - visudo, the build system requires sudo
pacman -S devtools - install devtools for building in clean chroot
mkdir -vp /home/build/scripts - create build directory
cp -var <where scripts are> /home/build/scripts - copy the scripts into
build directory
cd /home/build/scripts -
make mkchroot - uses mkarchroot to create clean chroot and checks out
the svn code
- if svn co failes then use make update to
complete the svn check out
make trinity - builds packages
here is the entry in the Makefile that installs the archroot create a
local repo and checks out the source
mkchroot:
sudo mkarchroot $(CHROOTDIR)/root base base-devel sudo
sudo mkdir $(CHROOTDIR)/root/repo
sudo chmod 777 $(CHROOTDIR)/root/repo
sudo mkdir $(CHROOTDIR)/trinity.source
sudo chmod 777 $(CHROOTDIR)/trinity.source
sudo mkdir -vp $(CHROOTDIR)/root/trinity.source
sudo chmod 777 $(CHROOTDIR)/root/trinity.source
(cd $(CHROOTDIR)/trinity.source; svn checkout
svn://anonsvn.kde.org/home/kde/branches/trinity ./)
(cd $(CHROOTDIR)/trinity.source; svn cleanup)
(cd $(CHROOTDIR)/trinity.source; svn update)
The mkarchroot is handled by the Builder.sh script
This updates the chroot
( sudo /usr/sbin/mkarchroot -u ${_chroot}/root 2>&1 | tee
${_date}build.log && exit ${PIPESTATUS} )
This builds the package in a clean chroot
( sudo /usr/sbin/makechrootpkg -c -r ${_chroot} 2>&1 | tee -a
${_date}build.log && exit ${PIPESTATUS} )
#!/bin/bash -e
_pgm=${0##*/} # whoami
_path=${0%/*} # fetch directory name = module name
_pwd=$(pwd)
_chroot="/home/build"
_date=$(date +%F)"-"$(date +%R)"-"
_repos="/home/build/root/repo"
_pkgname="*.pkg.tar*"
# Check parameters
#[ -n ${1} ] || ( echo "Missing package name arg: ${1}";exit 1 )
#[ -d ${_svnsrc}/${_module} ] || ( echo "Missing source directory:
${_svnsrc}/${_module}";exit 1 )
[ -d ${_path} ] || ( echo "Missing directory: ${_path}";exit 2 )
[ -f "${_path}/PKGBUILD" ] ||( echo "Missing PKGBUILD";exit 3 )
cd ${_path}
_date=""
rm build.log namcap.log filelist.log || true
# update chroot and build package
echo "Building---> ${_path}"
( sudo /usr/sbin/mkarchroot -u ${_chroot}/root 2>&1 | tee
${_date}build.log && exit ${PIPESTATUS} )
( sudo /usr/sbin/makechrootpkg -c -r ${_chroot} 2>&1 | tee -a
${_date}build.log && exit ${PIPESTATUS} )
# Namcap package
_pkg=$(find . -name "${_pkgname}" -print)
[ -f ${_pkg} ] || ( echo "Missing package: ${_pkgname}";exit 4 )
( /usr/bin/namcap ${_pkg} 2>&1 | tee ${_date}namcap.log && exit
${PIPESTATUS} )
( /bin/tar -tf ${_pkg} 2>&1 | tee ${_date}filelist.log && exit
${PIPESTATUS} )
# Me and my repo
mv -vf ${_pkg} ${_repos}
/usr/bin/repo-add ${_repos}/local.db.tar.gz ${_repos}/${_pkg}
exit 0
If you want to build without a clean chroot then just set the following
in each PKGBUILD file
_source="/trinity.source" - where the source is ex:
_source="/home/build/trinity.source/dependencies/tqtinterface"
_prefix="/usr" - where you want the package to install
_builddir=BUILD - where you want the out of source build directory ex:
_builddir="/tmp/builddir"
then
makepkg -c - builds it
package will be in the build directory
2:09 p.m.
New subject: [trinity-devel] kdegraphics CMake Status
On 30 April 2011 06:48, Baho Utot <baho-utot(a)columbus.rr.com> wrote:
On 04/29/2011 11:59 PM, Calvin Morrison wrote:
Thanks for explaining it!
Also Baho,
you don't seem to have included mkarchchroot, so i can't even use your
system.
Calvin Morrison
by running make in the scripts directory gives you the instructions for
using the system.
All that is needed is to
add the user to sudo - visudo, the build system requires sudo
pacman -S devtools - install devtools for building in clean chroot
mkdir -vp /home/build/scripts - create build directory
cp -var <where scripts are> /home/build/scripts - copy the scripts into
build directory
cd /home/build/scripts -
make mkchroot - uses mkarchroot to create clean chroot and checks out the
svn code
- if svn co failes then use make update to complete
the svn check out
make trinity - builds packages
here is the entry in the Makefile that installs the archroot create a local
repo and checks out the source
mkchroot:
sudo mkarchroot $(CHROOTDIR)/root base base-devel sudo
sudo mkdir $(CHROOTDIR)/root/repo
sudo chmod 777 $(CHROOTDIR)/root/repo
sudo mkdir $(CHROOTDIR)/trinity.source
sudo chmod 777 $(CHROOTDIR)/trinity.source
sudo mkdir -vp $(CHROOTDIR)/root/trinity.source
sudo chmod 777 $(CHROOTDIR)/root/trinity.source
(cd $(CHROOTDIR)/trinity.source; svn checkout
svn://anonsvn.kde.org/home/kde/branches/trinity ./)
(cd $(CHROOTDIR)/trinity.source; svn cleanup)
(cd $(CHROOTDIR)/trinity.source; svn update)
The mkarchroot is handled by the Builder.sh script
This updates the chroot
( sudo /usr/sbin/mkarchroot -u ${_chroot}/root 2>&1 | tee ${_date}build.log
&& exit ${PIPESTATUS} )
This builds the package in a clean chroot
( sudo /usr/sbin/makechrootpkg -c -r ${_chroot} 2>&1 | tee -a
${_date}build.log && exit ${PIPESTATUS} )
#!/bin/bash -e
_pgm=${0##*/} # whoami
_path=${0%/*} # fetch directory name = module name
_pwd=$(pwd)
_chroot="/home/build"
_date=$(date +%F)"-"$(date +%R)"-"
_repos="/home/build/root/repo"
_pkgname="*.pkg.tar*"
# Check parameters
#[ -n ${1} ] || ( echo "Missing package name arg: ${1}";exit 1 )
#[ -d ${_svnsrc}/${_module} ] || ( echo "Missing source directory:
${_svnsrc}/${_module}";exit 1 )
[ -d ${_path} ] || ( echo "Missing directory: ${_path}";exit 2 )
[ -f "${_path}/PKGBUILD" ] ||( echo "Missing PKGBUILD";exit 3 )
cd ${_path}
_date=""
rm build.log namcap.log filelist.log || true
# update chroot and build package
echo "Building---> ${_path}"
( sudo /usr/sbin/mkarchroot -u ${_chroot}/root 2>&1 | tee ${_date}build.log
&& exit ${PIPESTATUS} )
( sudo /usr/sbin/makechrootpkg -c -r ${_chroot} 2>&1 | tee -a
${_date}build.log && exit ${PIPESTATUS} )
# Namcap package
_pkg=$(find . -name "${_pkgname}" -print)
[ -f ${_pkg} ] || ( echo "Missing package: ${_pkgname}";exit 4 )
( /usr/bin/namcap ${_pkg} 2>&1 | tee ${_date}namcap.log && exit
${PIPESTATUS} )
( /bin/tar -tf ${_pkg} 2>&1 | tee ${_date}filelist.log && exit
${PIPESTATUS}
)
# Me and my repo
mv -vf ${_pkg} ${_repos}
/usr/bin/repo-add ${_repos}/local.db.tar.gz ${_repos}/${_pkg}
exit 0
If you want to build without a clean chroot then just set the following in
each PKGBUILD file
_source="/trinity.source" - where the source is ex:
_source="/home/build/trinity.source/dependencies/tqtinterface"
_prefix="/usr" - where you want the package to install
_builddir=BUILD - where you want the out of source build directory ex:
_builddir="/tmp/builddir"
then
makepkg -c - builds it
package will be in the build directory
1 May
1 May
8:17 p.m.
New subject: [trinity-devel] kdegraphics CMake Status
Hi Serghei,
I was just wondering when you think you might be able to wrap up
kdegraphics? I'd like to keep things moving if possible. :)
Thanks!
Tim
8:22 p.m.
New subject: [trinity-devel] kdegraphics CMake Status
On Sunday 01 May 2011 23:17:14 Timothy Pearson wrote:
Hi Serghei,
I was just wondering when you think you might be able to wrap up
kdegraphics? I'd like to keep things moving if possible. :)
Not sure, Calvin don't send me his work, yet. Right now I'm working on kdesdk.
Tim
--
Serghei
8:43 p.m.
New subject: [trinity-devel] kdegraphics CMake Status
On 04/29/2011 05:59 PM, Calvin Morrison wrote:
Tim,
I apologize for the delays, life seems to have caught up with me recently. This week and
the following are finals for the semester so I am under a great stress and large workload.
I also have not been able to successfully install Trinity either on Arch Linux. Baho and
David haven't grasped the concept of portability so I don't have it working.
Again Sorry,
Calvin Morrison.
Life does do that from time to time :) I'm in the process of going back through
all the PKGBUILDs and updating them. I have just managed to get Qt3 going again,
so it will take a few days to go through all the PKGBUILDs. I'm still not 100%
comfortable with my Qt3 build so that is my primary focus. I have it building,
but I need to shuttle some of the include file locations. I'll post my new
PKGBUILDs tonight and pass along a URL for testing.
I had Trinity building start to finish before the Qt3 and out-of-source
requirements on 7 different boxes, both i686 and x86_64 -- so I don't know how
much more portable I could make them. I have found a couple of ways to make them
more generic. We'll see how the next set do.
--
David C. Rankin, J.D.,P.E.
5 May
5 May
7:58 p.m.
New subject: [trinity-devel] kdegraphics CMake Status
Hi Serghei,
Have you received the kdegraphics CMake files from Calvin yet? If so,
when do you think you may have an initial CMake port in SVN to test?
Thanks!
Tim
8:02 p.m.
New subject: [trinity-devel] kdegraphics CMake Status
On Thursday 05 May 2011 22:58:18 Timothy Pearson wrote:
Hi Serghei,
Have you received the kdegraphics CMake files from Calvin yet? If so,
when do you think you may have an initial CMake port in SVN to test?
I did not received it yet.
--
Serghei
4739
days inactive
4745
days old
12 comments
5 participants
participants (5)
-
Baho Utot -
Calvin Morrison -
David C. Rankin -
Serghei Amelian -
Timothy Pearson