Update of /cvsroot/leaf/src/The_UnNamed_One/buildtool
In directory sc8-pr-cvs6.sourceforge.net:/tmp/cvs-serv15949/buildtool
Added Files:
COPYING Changes README TODO buildpacket.pl buildtool.pl
Log Message:
initial import
--- NEW FILE: buildpacket.pl ---
#! /usr/bin/perl -w
# TODO
# * replace GetOpt::Long with GetOpt?
# * additional switch --interactive, that will let the user make changes to
files,
# after everything is assembled, but before list-file and lrp-packed is
created
# * move buildtool downhttp and downcvs into classes, add downfile and allow
# buildpackage to dowload the files it needs
# $Header: /cvsroot/leaf/src/The_UnNamed_One/buildtool/buildpacket.pl,v 1.1
2008/03/01 16:24:13 hejl Exp $
use strict;
use warnings;
# INCLUDES
use Getopt::Long;
use Config::General;
use Data::Dumper;
[...1200 lines suppressed...]
=head1 NAME
buildpackage - create an lrp-package from the files created with buildtool
=head1 SYNOPSIS
B<buildpackage> --package=packagename --packager=name_of_packager
[--target=packagefile] [-lrp=existing.lrp] [--verbose]
=head1 DESCRIPTION
B<buildpackage> Creates a new lrp-file, using the files created with buildtool
Lists the contents of LEAF packages. The packages to be
=head1 SEE ALSO
http://leaf.sourceforge.net/doc/guide/bucd-buildpacket.html
=cut
--- NEW FILE: Changes ---
0.6pre2
- removed itrace support
- added builtin (perl based) file installation tracing for build and staging
dir,
disabled by default (enable via buildtool.conf)
0.6pre1
- added support for cvs ext (ssh)
- added support for overriding package config servers
- better commandline parsing
- cleanup of help message
- put itrace back in again (DISABLED by default)
- renamed global.cfg to sources.cfg
0.2-0.5:
- lots...
0.2pre4:
- show list of required sources/packages on screen
- minor cleanups in source_files
- added helloworld example (thanks to Luis F. Correia for this!)
- show a message to the screen if things are already built or sourced
- added support for setting env vars via buildtool.cfg (envname entry
in file section, thanks Martin!)
- added support for -f switch on commandline for building and sourcing
0.2pre3:
- changed describe so it tells us a bit more what is available
- fixed a typo in describe
- dlclean calls clean for each package
- added global.cfg servers to package/source in buildtool.cfgs
(no need to define them in there anymore)
- cleanups
- added the possibility to add defaults to sources and packages
0.2pre2:
- minor cleanups in the README
- add support for downloading removed (Attic) files via viewcvs and
auto detection for this
- fixed a bug that prevented files from being added to the required packagelist
- added upx to kernel buildfile
0.2pre1:
- put ther version into the logfile each time the buildtool starts
- changes to Readme
- cleanups in buildtool.pm , mostly build_files and source_files
to handle build dependencies (Required packages).
- added use strict
- moved buildtool.pm to buildtool dir and include buildtool::buildtool for now
0.1.2:
- changed all config vars to be handled as lowercase internally,
and use -LowerCaseNames when reading them in conf files
- fixed another bug in source_files
- 'dlclean' looks now at the installed packages not on the list
from the global.cfg
- the same is true for 'clean'
- added a edited var that is set to 0 when making a maketar,
to be sure people edit the config filÃe!
- check if there is source and package with same name, if so, die
0.1.1:
- fixed a warning in show_description
- fixed a bug in handling of the source dependencies (reported by K.-P.
Kirchdöfer <[EMAIL PROTECTED]>)
- started to reorganize the TODO file
0.1:
- added Copying and copyright notice
- added maketar command for distributing
of multiple servers)
easier to define one server for viewcvs and use Directory entries instead
- changed handling of directory entries in downloading (should make it
and building packages or sources twice.
- added support for a list of installed packages. This avoids downloading
- moved configs to conf dir
instead of 37m , this seems to work better for some terminals (Martin Hejl
<[EMAIL PROTECTED]>)
- changed the functions for giving back red and green text to use 39m
- changed usage message
- die if logfile cannot be opened
- make sure the log dir is created before writing to it
download files already there, quite useful for developing
- added OverwriteFiles to config, if set to 0 buildtool will not try to
0.1pre4:
the finished packages should go to.
- added PACKAGEDIR to mastermakefile and buildtool, this is where
by buildenv (and others).
- added export to the vars of the mastermakefile.mk as this is needed
and can be overwritten in the Makefiles (mk files)
before the host compiler... So PATH is now set as environment var
compiling a new buildenv fails as the cross-compiler is in the path
was calling make and setting PATH via commandline. When this is done,
- changed setting the PATH value when calling makefiles. Until now it
buildroot in much more easier.
it and no seperate source package. This makes putting new versions from
- changed the buildenv package: uclibc, gcc and binutils are now part of
- fixed a typo in make_distclean
0.1pre3:
- added distclean to buildtool commands
- added checkenv for doing some tests on startup.
else (for cross-gcc).
- added exporting of a path containing the staging dir before anything
sources.
- fixed a bug in build_files that prevented build step to be called for
--- NEW FILE: COPYING ---
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
--- NEW FILE: README ---
General:
========
This is the second attempt to build a tool to be able to build
bering-uclibc from scratch. The first one was heavily based on buildroot
from erik andersen (from uclibc.org), but this time things are a bit
different. This tool is mainly written in Perl, although it still uses Makefiles
and the buildenvironment is uses comes still from buildroot (which won't change
anyway)
Requirements:
=============
- a working compile environment gcc+binutils+libs
- wget
- fakeroot (you can find it in the tools directory)
- Perl (testesd only with 5.6.1)
Perl modules:
- Config::General (you can install it with perl -MCPAN -e 'install
Config::General')
- libvcs-perl > 1.00 , you can get it from
http://www.ucbering.de/download/libcvs-perl.tgz
Configuration:
==============
- Proxy: If you need to use a http proxy to download , please set the
environment var http_proxy according to it before you start buildtool,
e.g export http_proxy="http://proxy.example.com:8080/";
Note that at this time no user authentication for a proxy is supported.
Usage:
======
edit buildconf.cfg to adjust to your needs (especially the dir stuff).
start with a './buildtool.pl build buildenv ' to get a working build
environment. This will download the required sources for you automatically.
You can make a ./buildtool.pl --help to get a full listing of what is
supported now. To be honest, i already did this for you:
usage: ./buildtool.pl command [pkgname]|[srcname] [...]
commands:
describe [pkgname]|[srcname] shows descriptionlines of package
list shows a list of build/sourced packages and sources
[-f] source [pkgname]|[srcname] downloads, unpacks and patches
the wanted package/source
[-f] build [pkgname]|[srcname] the same as source, but builds
and installs sources/packages also
[-f] buildclean [pkgname]|[srcname] removes everything that is outside
the source dir
[-f] remove [pkgname|srcname] remove everything from dldir or all
distclean remove everything
maketar make a tar for distribution
The -f switch allows you to force building sourcing and cleaning
even if it seems the packages/sources are already installed or cleaned.
How things work:
================
First buildtool reads its config (buildtool.conf), after that it reads
the global.cfg file , which both reside in the conf subdir.
The global.cfg defines what packages and sources are out there
and how to find the buildtool.cfg file which must be provided for each
package. After that, buildtool searches for commands from the commandline.
Assume you make a './buildtool.pl build example-package' and the example-package
section (<Package example-package>) in the global.cfg says:
<Requires>
Name = example-src1
Name = example-src2
</Requires>
buildtool will download the sources and files for the two sources as well. So
first of all, it will download the buildtool.cfg file from the location
defined in global.cfg. It will download such a file for every packages/source
that should be downloaded and build. After that it will download all the files
defined in buildtool.cfg and place them in the source dir (in an subdir named as
the package, "source/example" for this example).
Having done that, the same is done for the Required packages (downloading
buildtool.cfg, downloading all files defined there).
Note that you have to define a file called buildtool.mk in the files section
as this is the one that will be used by buildtool to do a 'make source' later.
This leads us to the next step. Going into each source sub-directory and
calling a 'make -f ./buildtool.mk source'. This should unpack the sources
in this subdir, do the patching and whatever is needed to get a clean source
tree. But nothing is configured or made here, just unpacked.
A call to ./configure would be called by the next step , the build step.
buildtool goes into each subdir (like before) and do a
'make -f ./buildtool.mk build'
to have everything build. How the makefile actually make things is not
of any interest for us right now, thats the part of the file. It only
has to provide some targets (see doc/writing-mkfiles). Note that build
for any source dir is done before a 'make build' in the package directory
where the sources belog too (the programs should be compiled before they
are packed ;-)...
So that's how things (should) work.
Directories
===========
A few words about the directories in here:
source contains all the (unpacked and even compiled) sources
for both packages and sources, in subdirs named like
the package/source.
After compiling the sources should always be installed in:
build holds the installed programs that are used to build the
packages. Like in source there should be always a
subdir named as the package/source
staging This is the place where everything needed for compiling
should go, e.g. the gcc lives here as well as (at least
a copy of) all libraries that programs are compiled
against.
doc as you suggest, here is the documentation
make The mastermakefile (which sets some vars and should
be included in every mk file for soruces/packages) is here
nothing more right now
log In here you find the buildtoollog which is the logfile
of buildtool. Most messages (and errors) go here, so
you might want to have a look if things go wrong (
or if they don't - if you like ;-)
package In here you will find the builded packages, ready to
use
conf the buildtool config files are here (buildtool.conf,
global.conf, and installed)
tools includes some toolÃs that are needed to build stuff
Developing
==========
A few words how you can use this for developing new packages. Perhaps i should
mention first that there is a switch in the buildtool.conf that can be used
to prevent buildtool from overwriting existing files. If this (OverwriteFiles)
is set to 0 buildtool will not overwrite anything, but it will also not
download. This is ment to be used if you are a developer and want to change
the buildtool or patchfiles before updating them on the server. If you don't
use it, buildtool will overwrite your work and that's mostly not what you
wish.
If you wish (for whatever reason) to use the buildtool.mk file to build
by hand you should call it with something like:
'make -f buildtool.mk source BT_BUILDROOT=/my/example/dir \
MASTERMAKEFILE=/my/example/dir/make/MasterInclude.mk'
or export the BT_BUILDROOT and MASTERMAKEFILE vars into the environment.
If you do this , everything should be fine (at least if your makefiles are
o.k. ;-)
@FIXME@ write more about developing a new package!
Copying
=======
Please have a look at the file COPYING in this directory
(C) 2003-2004 Arne Bernin & Martin Hejl
--- NEW FILE: buildtool.pl ---
#! /usr/bin/perl -w
# $Id: buildtool.pl,v 1.1 2008/03/01 16:24:13 hejl Exp $
# main program buildtool2 for uclibc-bering
# (C) 2003 Arne Bernin
# This software is distributed under the GNU General Public Licence,
# please see the file COPYING
use File::Basename;
use File::Spec;
use buildtool::buildtool;
use buildtool::Clean;
use buildtool::Make::Tar;
use buildtool::Make::Source;
use buildtool::Make::Build;
use buildtool::Make::PackageList;
use buildtool::Config;
use Config::General qw(ParseConfig);
use strict;
use vars ('%globConf');;
####################################################################################################################
BEGIN {
my $lockfile = "conf/lockfile";
# check for lockfile:
if (-f $lockfile){
die("\nIt seems you are already running another instance of
buildtool, please wait until it finished!\n".
"if this is not true, please remove the $lockfile file
yourself\n\n");
}
# else touch lockfile
die("making lockfile failed:".$!) if (system("touch $lockfile") != 0);
};
END {
my $errvar=$?;
my $lockfile = "conf/lockfile";
# whatever happens, remove lockfile
die("removing lockfile failed:".$!) if (system("rm -f $lockfile") != 0);
exit($errvar);
}
#####################################################################################################################
# load my conf
%globConf = Config::General::ParseConfig("-ConfigFile" =>
"conf/buildtool.conf", "-LowerCaseNames" => 1);
# find out what our root-dir is and inject it into the config
$globConf{'root_dir'} = File::Spec->rel2abs(
File::Basename::dirname($0)
);
# make sure, log dir is there:
log_dir_make();
# read in global file-config
my %sourcesConfig = Config::General::ParseConfig("-ConfigFile" =>
strip_slashes(make_absolute_path($globConf{globalconffile})), "-LowerCaseNames"
=> 1);
sub usage {
print <<MYEOF
usage: $0 [option] command [pkgname|srcname] [...]
commands:
describe [pkgname|srcname]\t shows descriptionlines of package
list \t\t\t\t shows a list of built/sourced packages and sources
source [pkgname|srcname] \t downloads, unpacks and patches
\t the wanted package/source
build [pkgname|srcname] \t the same as source, but builds
\t and installs sources/packages also
pkglist [pkgname|srcname] \t create a list with all dependencies
\t for the package given or all if no name given
buildclean [pkgname|srcname]\t removes everything that is outside
\t the source dir
srcclean [pkgname|srcname]\t same as buildclean + call make srcclean
remove [pkgname|srcname]\t same as buildclean + remove everything from dldir
distclean \t remove everything
maketar \t make a tar for distribution
options:
-v \t just print version and exit
-f \t allows you to force the command even if the
internal
\t state of buildtool states it has nothing to do
-O \t Do not override default Server entries with the
ones
\t found in package/source buildtool config
-D \t Download nothing, use files in Source dir (useful
for devel)
-d \t Only to be used in conjunction with the "source"
target.
\t Only download files, don't invoke the source
action on buildtool.mk
MYEOF
;
exit(1);
}
# parse commandline commands.
# we know the following:
# command status
# =================================================
# describe [Packagename] ok shows descriptionlines of package
# source [Packagename|Sourcename] ok downloads, unpacks and patches
# the wanted package/source
# build [Packagename|Sourcename] ok the same as source, but builds
# and installs sources/packages
# clean [Packagename|Sourcename] ok make a make clean in srcdir
# dlclean [Packagename|Sourcename] ok remove everything from dldir
# NI=not implemented
# now it seems we are really starting, lets put a message in
# the logfile , logdir should be created by check_env
logme("==================================================");
logme("buildtool Version ". $globConf{version} ." starting");
logme(scalar localtime);
&usage() if ($#ARGV < 0);
# check the
while ( $ARGV[0] and $ARGV[0] =~ /^-.*/ ) {
my $option = $ARGV[0];
$option =~ s/^-(.*)$/$1/;
debug("option -$option given");
shift;
# now switch according to option:
if ($option eq "v" or $option eq "-version") {
print "Version:". $globConf{version} . "\n";
exit (0);
} elsif ($option eq "h" or $option eq "-help") {
&usage();
} elsif ($option eq "f") {
$globConf{'force'} = 1;
} elsif ($option eq "D") {
$globConf{'nodownload'} = 1;
} elsif ($option eq "O") {
$globConf{'noserveroverride'} = 1;
} elsif ($option eq "d") {
$globConf{'downloadonly'} = 1;
} else {
print buildtool::Common::Object::make_text_red('',"Error:" ) .
" Unknown Option -" . $option . "\n\n";
exit(1);
}
}
# check the environment
&check_env();
#???
# put in the default config stuff
my $configClass = buildtool::Config->new(\%globConf, \%sourcesConfig);
$configClass->adjustFileConfig();
# now search for real commands:
if ($ARGV[0] eq "describe") {
# show descriptions
shift;
$configClass->showDescription(@ARGV);
} elsif ($ARGV[0] eq "list") {
# show descriptions
shift;
my $list = buildtool::Common::InstalledFile->new(\%globConf);
$list->showList();
} elsif ($ARGV[0] eq "source") {
# source packages/sources
shift;
my $make = buildtool::Make::Source->new(\%globConf, \%sourcesConfig);
$make->make(@ARGV);
} elsif ($ARGV[0] eq "pkglist") {
# just print packagelist (useful fpr other tools)
shift;
my $make = buildtool::Make::PackageList->new(\%globConf, \%sourcesConfig);
$make->make(@ARGV);
} elsif ($ARGV[0] eq "build") {
# build packages/sources
shift;
# first do a make source:
check_lib_link();
my $source = buildtool::Make::Source->new(\%globConf, \%sourcesConfig);
$source->make(@ARGV);
# now do a make build...
my $make= buildtool::Make::Build->new(\%globConf, \%sourcesConfig);
$make->make(@ARGV);
} elsif ($ARGV[0] eq "buildclean") {
# buildclean package/source
shift;
my $clean = buildtool::Clean::Buildclean->new(\%globConf);
$clean->clean(@ARGV);
} elsif ($ARGV[0] eq "srcclean") {
# srcclean package/source
shift;
my $clean = buildtool::Clean::Srcclean->new(\%globConf);
$clean->clean(@ARGV);
} elsif ($ARGV[0] eq "remove") {
# remove package/source
shift;
my $clean = buildtool::Clean::Remove->new(\%globConf);
$clean->clean(@ARGV);
} elsif ($ARGV[0] eq "maketar") {
# make a tar file
my $make = buildtool::Make::Tar->new(\%globConf);
$make->make();
} elsif ($ARGV[0] eq "distclean") {
# make it distclean
print "\nAre you sure you want to delete everything you've downloaded and
built? (y/N) ";
my $ask = <STDIN>;
chop $ask;
if ($ask eq "y" or $ask eq "Y" or $ask eq "j" or $ask eq "J") {
print "making distclean:\n" ;
my $clean = buildtool::Clean::Distclean->new(\%globConf);
$clean->clean();
}
} else {
# unknown command
print "\nunknown command " . $ARGV[0] . "!\n\n";
usage();
}
--- NEW FILE: TODO ---
0.?
- remove build dir and use (if needed) internal build dirs in the source
directories
(like debian does).
0.7:
- add support for continue building even if a package build failes (can be used
for automatic/nightly building of all sources)
- add support for automatically build the packages (call buildpacket)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
leaf-cvs-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits
