--- elfrc-0.7.orig/debian/elfrc.manpages +++ elfrc-0.7/debian/elfrc.manpages @@ -0,0 +1 @@ +debian/elfrc.1 --- elfrc-0.7.orig/debian/changelog +++ elfrc-0.7/debian/changelog @@ -0,0 +1,5 @@ +elfrc (0.7-1) unstable; urgency=low + + * Initial release (Closes: #432964) + + -- Krzysztof Burghardt Thu, 18 Sep 2008 20:18:01 +0200 --- elfrc-0.7.orig/debian/compat +++ elfrc-0.7/debian/compat @@ -0,0 +1 @@ +5 --- elfrc-0.7.orig/debian/watch +++ elfrc-0.7/debian/watch @@ -0,0 +1,2 @@ +version=3 +http://ktown.kde.org/~frerich/elfrc.html elfrc-(.*)\.tar\.gz --- elfrc-0.7.orig/debian/rules +++ elfrc-0.7/debian/rules @@ -0,0 +1,44 @@ +#!/usr/bin/make -f +# -*- makefile -*- + +#export DH_VERBOSE=1 + +build: build-stamp +build-stamp: + dh_testdir + $(MAKE) + touch $@ + +clean: + dh_testdir + dh_testroot + rm -f build-stamp + $(MAKE) clean + dh_clean + +install: build + dh_testdir + dh_testroot + dh_clean -k + install -m 755 -D elfrc debian/elfrc/usr/bin/elfrc + +binary-indep: build install + +binary-arch: build install + dh_testdir + dh_testroot + dh_installchangelogs + dh_installdocs + dh_installman + dh_strip + dh_compress + dh_fixperms + dh_installdeb + dh_shlibdeps + dh_gencontrol + dh_md5sums + dh_builddeb + +binary: binary-indep binary-arch + +.PHONY: build clean binary-indep binary-arch binary install --- elfrc-0.7.orig/debian/elfrc.1 +++ elfrc-0.7/debian/elfrc.1 @@ -0,0 +1,60 @@ +.TH "ELFRC" "1" +.SH "NAME" +elfrc \(em a resource compiler for ELF systems +.SH "SYNOPSIS" +.PP +\fBelfrc\fR [\fB-o \fIfilename\fR\fP] [\fB-h \fIfilename\fR\fP] [\fB-v \fP] +.SH "DESCRIPTION" +.PP +This manual page documents briefly the +\fBelfrc\fR command. +.PP +This manual page was written for the \fBDebian\fP distribution +because the original program does not have a manual page. + +.PP +\fBelfrc\fR is a program which can +turn arbitrary files into ELF object files which can then be +linked into your program directly and accessed via simple, +user-defined symbol names. + +For instance, it's possible to embed even huge (16MB+) files +directly into the executable and then access the data in constant +time without making the compiler or linker eat loads of memory. +.SH "OPTIONS" +.PP +Here's what the arguments do: +.IP "\fB-o\fP \fIfilename\fR " 10 +Store resulting ELF object in \fIfilename\fR. If not +given, no ELF object will be generated. +.IP "\fB-h\fP \fIfilename\fR " 10 +Store C header file which can be used to access the resource data in +\fIfilename\fR. If not given, no header +file will be generated. +.IP "\fB-v\fP " 10 +Be a little verbose about what's going on. +.PP +In any case, the most important argument is \fIresfile\fR \- the path +to a resource file which can be parsed by elfrc. If no +resource file is given, or if "\-" (a dash) is given, the +resources will be read from the standard input. +.PP +A resource file is just a plain text file, each line in the +file describing a resource to be compiled into the ELF output. Each +line is expected to three fields, separated by tab characters: the +type of the resource (can be either 'binary' or 'text'), the symbol +name (this should be a valid C identifier) and the path to the file +to be compiled in. +.SH "AUTHOR" +.PP +This manual page was written by Kumar Appaiah akumar@ee.iitm.ac.in for +the \fBDebian\fP system (but may be used by others). Permission is +granted to copy, distribute and/or modify this document under +the terms of the GNU General Public License, Version 2 any +later version published by the Free Software Foundation. + +.PP +On Debian systems, the complete text of the GNU General Public +License can be found in /usr/share/common-licenses/GPL. + +.\" created by instant / docbook-to-man, Tue 17 Jul 2007, 15:19 --- elfrc-0.7.orig/debian/copyright +++ elfrc-0.7/debian/copyright @@ -0,0 +1,39 @@ +This package is based on package debianized by Kumar Appaiah + on Tue, 17 Jul 2007 14:35:20 +0530. + +It was downloaded from http://ktown.kde.org/~frerich/elfrc.html + +Upstream Author: + + Frerich Raabe + +Copyright: + + Copyright © 2006 Frerich Raabe + +License: + + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + + 1. Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. + 2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. + + THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR + IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES + OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. + IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, + INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT + NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, + DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY + THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT + (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF + THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +The Debian packaging is © 2007, Kumar Appaiah +and © 2008, Krzysztof Burghardt +is licensed under the GPL, see `/usr/share/common-licenses/GPL'. --- elfrc-0.7.orig/debian/elfrc.docs +++ elfrc-0.7/debian/elfrc.docs @@ -0,0 +1 @@ +README --- elfrc-0.7.orig/debian/control +++ elfrc-0.7/debian/control @@ -0,0 +1,19 @@ +Source: elfrc +Section: utils +Priority: optional +Maintainer: Krzysztof Burghardt +Build-Depends: debhelper (>= 5) +Standards-Version: 3.8.0 +Homepage: http://ktown.kde.org/~frerich/elfrc.html + +Package: elfrc +Architecture: any +Depends: ${shlibs:Depends}, ${misc:Depends} +Description: convert arbitrary files into elf objects + elfrc is a program which can turn arbitrary files into ELF object files which + can then be linked into your program directly and accessed via simple, + user-defined symbol names. + . + For instance, it's possible to embed even huge (16MB+) files directly into the + executable and then access the data in constant time without making the + compiler or linker eat loads of memory.