Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I haven't been able to find a howto on the wiki or a message in the forum on how to create a funplug package.
Assuming a cross-compile environment produced with the instructions given at http://dns323.kood.org/howto:crosscompile, what is the best way to build a funplug package?
Offline
steveG wrote:
I haven't been able to find a howto on the wiki or a message in the forum on how to create a funplug package.
Assuming a cross-compile environment produced with the instructions given at http://dns323.kood.org/howto:crosscompile, what is the best way to build a funplug package?
http://www.inreto.de/dns323/fun-plug/0.5/
Follow the instruction there ![]()
Offline
starry_knight - there is a difference between installing fun_plug and creating a fun_plug package - fun_plug is a simple script, but someone has to create the software that fun_plug calls , and that is what he is asking about.
Last edited by fordem (2008-05-31 18:47:58)
Offline
i dont know if this is the right method but i created ffp and oteher needed directories (like share, etc, start) in my tmp. then put all the files where they belong (in right directories) and after you finished execute
#tar cvzf package_name-version-ffp0.5.tgz ffp
that worked so i was a happy panda ![]()
Offline
SilentException:
DId you just use --prefix and --exec-prefix when you ran ./configure to point to your /tmp/ffp or did you need do other stuff as well?
Offline
I'm using funplug-0.5 and when compiling packages for it I do the following:
First step is to configure the program in question with the --prefix option:
./configure --prefix=/ffp/devel/releases/Toolname-ffp0.5/ffp make make install
After compiling all binaries and additional files will be "installed" in the above directory.
Don't forget to add a "start" folder with a proper toolname.sh for automatic startup.
To create the actual package, there's a rather lengthy command:
tar cf - -C /ffp/devel/releases/Toolname --owner=root --group=root . | gzip - -c >toolname-0.1.0-ffp0.5.tgz
It may be possible to shorten this, I didn't feel like it yet though :)
Offline
KyleK wrote:
Code:
./configure --prefix=/ffp/devel/releases/Toolname-ffp0.5/ffp
No. This will fail for quite a few packages. You should always use '--prefix=/ffp'. prefix denotes the _final_ install location. Many programs use this path to look for files at run-time, so it must be /ffp.
KyleK wrote:
Code:
make installAfter compiling all binaries and additional files will be "installed" in the above directory.
Installing into a separate tree, and creating a tarball from it is a good way to create the package. The proper way (for many, but not all packages) to install to a separate tree is known as DESTDIR:
make DESTDIR=/ffp/devel/releases/Toolname/ install
This works for many autoconf-based packages. Other packages may required 'make prefix=/ffp/devel/releases/Toolname/ffp install', and some may not support separate install trees at all.
Offline
Well, I certainly can't speak for many apps, and you've obviously made way more packages than I did, but so far my method proved successful in that no app complained so far ![]()
Thank you for these hints though, that's actually the first time someone "in the know" commented on the packaging process. All that stuff is missing in the Wiki.
Offline