[HELP] Script for automated compiling
Hi, I've been trying to make a script to compile a few softwares but it doesn't seem to work. Here is the script:
Code:
for package in $(cat /source/graphics) Code:
jpegsrc.v6b.tar.gz Thanks in advance |
How about telling us where/how it fails? I'm not inclined to download
those so I can test what your issue might be... Cheers, Tink |
For instance the tar listing won't work w/o the right decompressor arg and you're listing but not unpacking.
Code:
#set -xe |
recent versions of tar (1.15.1 for instance) pick the archive format
automagically ... :} Cheers, Tink |
recent versions of tar (1.15.1 for instance) pick the archive format automagically ... :}
Awesome. |
First of all, thanks to all those speedy replies;). I gave up on that script after realising that a Makefile does the job 2x better :p (I mean with the logs and output redirection). If anyone is interested, I will post later a sample of my makefile. Once again thanks a million. |
If anyone is interested, I will post later a sample of my makefile.
Since you've been given help here the least you can try to "repay"* with would be doing just that. * OK, we have no concept of "paying" for "services" but you know what I mean. |
I'll do exactly that ;) . Thanks once again.
|
Here's a little project I whipped up for doing that:
http://distro.ibiblio.org/pub/linux/...2-noarch-1.tgz |
gee, thanks alot! The tool you've linked above is A1. btw, here is a portion of my Makefile: Code:
PKGDIR=`head -n 1 /source/packed | cut -f1 -d'/'` what I actually want to do is to make different Makefiles for the different tarballs and use the top-level Makefile to call the "other" Makefiles. Thanks in advance. p.s. I've used pkgbuild to create some packages for my zenwalk, and it works like a charm. thanks! |
Each package needs to be handled individually or things get way complicated. I have some pkgbuild scripts which make mega-packages or multiple pks from one or two source-dirs, but it really gets complicated. You should only do this where it's really necessary like for glibc or util-linux.
What pkgbuild does is put all the repetitive code out of the way in functions. This leaves the script very brief for normal autoconf pkgs which compile okay, with only pkg name and version details which distinguish it from another script. Any special options or added code between functions is easily added and seen. You'll also find examples for group and chain build scripts which will build all the pkgs from a text-file list or in the current working dir. |
All times are GMT -5. The time now is 04:40 PM. |