MobileRead Forums - View Single Post

knc1 · 05-17-2012, 01:39 PM

On building a static linked mc:
http://namelythehedgehog.wordpress.c...ght-commander/

Note that author did not know about the DESTDIR= build variable, using it would have avoided his packaging problem. You might have to ask Google, but the quick hints:

Code:

mkdir /tmp/new_name
make DESTDIR=/tmp/new_name install

Now go to /tmp/new_name and the tree below that directory is relative to the root directory of the system on which the software is to be installed.

For a static build, you should only find the single application file.
For a dynamicly linked build, you will find one or more files.
Works for any Autotools package, not just mc.
Ref:
http://www.gnu.org/prep/standards/ht...e/DESTDIR.html

05-17-2012, 01:39 PM	#7
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	On building a static linked mc: http://namelythehedgehog.wordpress.c...ght-commander/ Note that author did not know about the DESTDIR= build variable, using it would have avoided his packaging problem. You might have to ask Google, but the quick hints: Code: mkdir /tmp/new_name make DESTDIR=/tmp/new_name install Now go to /tmp/new_name and the tree below that directory is relative to the root directory of the system on which the software is to be installed. For a static build, you should only find the single application file. For a dynamicly linked build, you will find one or more files. Works for any Autotools package, not just mc. Ref: http://www.gnu.org/prep/standards/ht...e/DESTDIR.html Last edited by knc1; 05-17-2012 at 02:04 PM.