On Sat, 2011-09-10 at 04:53 +0200, Denys Vlasenko wrote:
> On Tuesday 06 September 2011 20:23, Christopher Barry wrote:
> > The path listed in the "make install behavior" defaults to ./_install.
> > Does --install symlink creation use this as well, or does it always use
> > '/'?
>
>
> if (ENABLE_FEATURE_INSTALLER && strcmp(argv[1], "--install") == 0) {
> int use_symbolic_links;
> const char *busybox;
>
> busybox = xmalloc_readlink(bb_busybox_exec_path);
> if (!busybox) {
> /* bb_busybox_exec_path is usually "/proc/self/exe".
> * In chroot, readlink("/proc/self/exe") usually
> fails.
> * In such case, better use argv[0] as symlink target
> * if it is a full path name.
> */
> if (argv[0][0] != '/')
> bb_error_msg_and_die("'%s' is not an absolute
> path", argv[0]);
> busybox = argv[0];
> }
> /* busybox --install [-s] [DIR]:
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> * -s: make symlinks
> * DIR: directory to install links to
> */
> use_symbolic_links = (argv[2] && strcmp(argv[2], "-s") == 0
> && argv++);
> install_links(busybox, use_symbolic_links, argv[2]);
> return 0;
> }
>
>
--
Thanks!
-C
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
