Always include a loader_path to Frameworks on macOS (so users can install

libraries there-in).  Include executable_path also even though this was a
harmless mistake.

Author: eliotmiranda

build.macos32x86/common/Makefile.app

@@ -168,8 +168,8 @@ $(APP)/Contents/Resources/%.icns: $(OSXDIR)/%.icns
 	cp -p $< $(APP)/Contents/Resources
 
 pathapp:
-	-test -d $(APP)/Contents/Frameworks && \
 	install_name_tool -add_rpath @executable_path/../Frameworks $(VMEXE)
+	install_name_tool -add_rpath @loader_path/../Frameworks $(VMEXE)
 
 # To sign the app, set SIGNING_IDENTITY in the environment, e.g.
 # export SIGNING_IDENTITY="Developer ID Application: Eliot Miranda"

build.macos64x64/common/Makefile.app

@@ -168,8 +168,8 @@ $(APP)/Contents/Resources/%.icns: $(OSXDIR)/%.icns
 	cp -p $< $(APP)/Contents/Resources
 
 pathapp:
-	-test -d $(APP)/Contents/Frameworks && \
 	install_name_tool -add_rpath @executable_path/../Frameworks $(VMEXE)
+	install_name_tool -add_rpath @loader_path/../Frameworks $(VMEXE)
 
 # To sign the app, set SIGNING_IDENTITY in the environment, e.g.
 # export SIGNING_IDENTITY="Developer ID Application: Eliot Miranda"