Intel Mac build error caused by meta_parser about piccolo

[younif]

just cp engine/bin/macOS/libclang.dylib to /usr/local/lib
it works for me

[BoomingTech-YuqiaoZhang]

If you are hasty, you may use this repository. Github Workflow shows "build macos" is passing.

If you are hasty, you may use this repository. Github Workflow shows "build macos" is passing.

[BoomingTech-YuqiaoZhang]

libclang.dylib is on the same path as meta_parser, you can use command:

cd /.../Pilot/engine/bin/macOS
install_name_tool -add_rpath /.../Pilot/engine/bin/macOS ./meta_parser

This works for me.

The following command is much better:
install_name_tool -rpath "/Users/hywei/Workspace/metaparser-master/Parser/../3rd_party/LLVM/lib/macOS" '@executable_path' ./engine/bin/macOS/meta_parser'

[begoss]

libclang.dylib is on the same path as meta_parser, you can use command:

cd /.../Pilot/engine/bin/macOS
install_name_tool -add_rpath /.../Pilot/engine/bin/macOS ./meta_parser

This works for me.

[BoomingTech-YuqiaoZhang]

is MacOS 12.2 needed? @BoomingTech-YuqiaoZhang running meta_parser on MacOS 11.6 throw the error

libc++.1.dylib is missing, I am fixing now

[BoomingTech-YuqiaoZhang]

is MacOS 12.2 needed? @BoomingTech-YuqiaoZhang running meta_parser on MacOS 11.6 throw the error

A merge request is provided. If you are hasty, you may use this repository

[BoomingTech-YuqiaoZhang]

For M1 developers, running these commands works for a temporary fix.

chmod +x .engine/bin/macOS/meta_parser
sudo cp engine/bin/macOS/libclang.dylib /usr/local/lib

A pull request has been provided. If you are hasty, you may use this repository first. The github workflow shows "build linux" is passing.

[iaomw]

[Yestercafe]

Change the missing dylib path, this can help you:
https://stackoverflow.com/questions/17703510/dyld-library-not-loaded-reason-image-not-found

[BoomingTech-YuqiaoZhang]

You can use the following commands to fix the build error on Linux temporarily. A merge request will be provided later.
chmod +x build_linux.sh
chmod +x "./engine/bin/Linux/meta_parse"
chrpath -r '$ORIGIN' "./engine/bin/Linux/meta_parser"
chmod +x "engine/3rdparty/VulkanSDK/bin/Linux/glslangValidator"

[BoomingTech-YuqiaoZhang]

If you are hasty, you may use this repository instead

[BoomingTech-YuqiaoZhang]

You can use the following commands to fix the build error on MacOS temporarily
chmod +x "./engine/bin/MacOS/meta_parse"
install_name_tool -rpath "/Users/hywei/Workspace/metaparser-master/Parser/../3rd_party/LLVM/lib/macOS" '@executable_path' './engine/bin/macOS/meta_parser'

[iaomw]

You can use the following commands to fix the build error on MacOS temporarily chmod +x "./engine/bin/MacOS/meta_parse" export LD_LIBRARY_PATH=./engine/bin/macOS${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}

Thanks, but it's the same result. I may try another solution using otool for libclang.dylib
But ultimately the project script should take care itself.

https://stackoverflow.com/questions/24045633/dyld-library-not-loaded-error

[deepkolos]

is MacOS 12.2 needed? @BoomingTech-YuqiaoZhang
running meta_parser on MacOS 11.6 throw the error

[iaomw]

just cp engine/bin/macOS/libclang.dylib to /usr/local/lib it works for me

Tested with cp command and manual copy, not working. What is your software version?

[BoomingTech-YuqiaoZhang]

You can use the following commands to fix the build error on MacOS temporarily chmod +x "./engine/bin/MacOS/meta_parse" export LD_LIBRARY_PATH=./engine/bin/macOS${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}

Thanks, but it's the same result. I may try another solution using otool for libclang.dylib But ultimately the project script should take care itself.

https://stackoverflow.com/questions/24045633/dyld-library-not-loaded-error

LB_LIBRARY_PATH may not work, you may use the following install_name_tool instead.
install_name_tool -rpath "/Users/hywei/Workspace/metaparser-master/Parser/../3rd_party/LLVM/lib/macOS" '@executable_path' './engine/bin/macOS/meta_parser'

[Kingfish404]

macOS 12.3.1 Intel i5 working with fellowing shell command

chmod +x "./engine/bin/MacOS/meta_parser"
cmake -S engine -B build -G "Xcode"
cp engine/bin/macOS/libclang.dylib /usr/local/lib
cmake --build build --config "${CMAKE_ARG_BUILD_TYPE_CONFIG}"
rm /usr/local/lib/libclang.dylib

then

./bin/PilotEditor

running.

Pic demo with still some problem

[BoomingTech-YuqiaoZhang]

is MacOS 12.2 needed? @BoomingTech-YuqiaoZhang running meta_parser on MacOS 11.6 throw the error

using the following commands to fix the libclang.dylib:
install_name_tool -change '/usr/lib/libc++.1.dylib' '@rpath/libc++.1.dylib' './engine/bin/macOS/libclang.dylib'
install_name_tool -rpath '@loader_path/../lib' '@executable_path' './engine/bin/macOS/libclang.dylib'

Then, download the missed libc++.1.dylib from the LLVM official web page

[BoomingTech-YuqiaoZhang]

is MacOS 12.2 needed? @BoomingTech-YuqiaoZhang running meta_parser on MacOS 11.6 throw the error

I am using the "objdump -p" to check the dependency of the libclang.dylib, and I find that the libz and libcursor are missing as well.

[BoomingTech-YuqiaoZhang]

is MacOS 12.2 needed? @BoomingTech-YuqiaoZhang running meta_parser on MacOS 11.6 throw the error

If you are hasty, you may use this repository. Github Workflow shows "build macos" is passing.

[BoomingTech-YuqiaoZhang]

A pull request is provided.

[forkercat]

For M1 developers, running these commands works for a temporary fix.

chmod +x .engine/bin/macOS/meta_parser
sudo cp engine/bin/macOS/libclang.dylib /usr/local/lib

[BoomingTech-YuqiaoZhang]

For M1 developers, running these commands works for a temporary fix.

chmod +x .engine/bin/macOS/meta_parser
sudo cp engine/bin/macOS/libclang.dylib /usr/local/lib

This is NOT recommended. The path "/usr/local/lib" may not exist if the user doesn't use homebrew or macport.
And the version of the libclang.dylib provided by us may be different from the libclang.dylib provided by homebrew or macport. Some other software may not work properly due to the confliction of the libs.

[BoomingTech-YuqiaoZhang]

just cp engine/bin/macOS/libclang.dylib to /usr/local/lib it works for me

This is NOT recommended. The path "/usr/local/lib" may not exist if the user doesn't use homebrew or macport.
And the version of the libclang.dylib provided by us may be different from the libclang.dylib provided by homebrew or macport. Some other software may not work properly due to the confliction of the libs.

[hyv1001]

This issue should have been fixed by #53, you can reopen or create a new ticket if it still exists on your machine