Use future-proof lib path in build-osx-libs.sh. Patch by trompetin17.
There are symbolic links to the library binaries in the directory dist/lib. It's better to use these links rather than the location they point to for the copy command (they point to a different location in ESR31). Refs #2462 This was SVN commit r16153.
This commit is contained in:
parent
993d9c72d3
commit
ba14819191
@ -701,7 +701,7 @@ then
|
||||
# js-config.h is different for debug and release builds, so we need different include directories for both
|
||||
mkdir -p $INCLUDE_DIR_DEBUG
|
||||
cp -R -L dist/include/* $INCLUDE_DIR_DEBUG/
|
||||
cp *.a $INSTALL_DIR/lib
|
||||
cp dist/lib/*.a $INSTALL_DIR/lib
|
||||
popd
|
||||
mv Makefile.in.bak Makefile.in
|
||||
mv shell/Makefile.in.bak shell/Makefile.in
|
||||
@ -714,7 +714,7 @@ then
|
||||
# js-config.h is different for debug and release builds, so we need different include directories for both
|
||||
mkdir -p $INCLUDE_DIR_RELEASE
|
||||
cp -R -L dist/include/* $INCLUDE_DIR_RELEASE/
|
||||
cp *.a $INSTALL_DIR/lib
|
||||
cp dist/lib/*.a $INSTALL_DIR/lib
|
||||
popd
|
||||
mv Makefile.in.bak Makefile.in
|
||||
mv shell/Makefile.in.bak shell/Makefile.in
|
||||
|
Loading…
Reference in New Issue
Block a user