Is this the proper way to make bear relocatable?

[leleliu008]

I want to use a prebuild Bear rather than build it locally.

I do this:

mv bin/bear bin/bear.exe

cat > bin/bear <<EOF
#!/bin/sh

set -ex

DIR="\$(cd "\$(dirname "\$0")" && pwd)"

if [ "\$1" = intercept ] || [ "\$1" = citnames ] ; then
    "\$DIR/bear.exe" "\$@"
else
                  "\$DIR/bear.exe" \
    --bear-path   "\$DIR/bear" \
    --library     "\$DIR/../lib/bear/libexec.dylib" \
    --wrapper     "\$DIR/../lib/bear/wrapper" \
    --wrapper-dir "\$DIR/../lib/bear/wrapper.d" \
    "\$@"
fi
EOF

Is this the proper way to make bear relocatable?

[rizsotto]

Not sure I understand the question. (I don't understand the "relocatable" word in this context.) Could you rather tell what you would like to achieve?

[leleliu008]

here the word "relocatable" means the installed files can be moved/copied to other locations.

[rizsotto]

Thanks to clarify that... what's the motivation to do the relocation?

Anyway... it's less work to recompile and specify the install directory IMO. But you can do this way. If it works, it works! 😄

[leleliu008]

what's the motivation to do the relocation?

It is nessasary to make bear relocatable to reduce the build time especially when building on QEMU.

I write a portable (can run on GNU/Linux, macOS, FreeBSD, OpenBSD, NetBSD, etc) build tool using bear, I don't want to build it on user's machine, because it has many dependencies, it will be hard to maintain and take much time to compile it. I also don't want to touch any system packager to install it, because there are various different package managers, it will be hard to maintain. I want to use my own build of it and install it to user's HOME directory. you known HOME directory is not a fixed location.

[leleliu008]

If it works, it works! 😄

It works for me.

Thanks for your replay.