命令行运行Python脚本时导入SWIG生成的ETPython模块报错求助

Let's break down what's happening here and walk through actionable fixes step by step.

First, Understand the Root Cause #

The _NSLog symbol error isn't actually a pure path issue — it's a linking problem with your SWIG-generated shared library (_ETPython.so). _NSLog is an Objective-C function from Apple's Foundation framework, which means your underlying C/C++ code (wrapped by SWIG) calls this function, but the shared library wasn't linked against the Foundation framework during compilation.

IDE environments like PyCharm or Squish often auto-configure extra linker flags or inherit system-level framework paths that plain terminal sessions don't, which explains why the module works there but fails in the terminal. The path fixes you tried helped with module discovery, but didn't address the missing framework dependency at the core of the error.

Step 1: Fix the Shared Library Linking #

You need to recompile the SWIG module with the correct linker flag to include the Foundation framework. Update your compilation command to add -framework Foundation:

Example Compilation Flow #

# Generate SWIG wrapper code
swig -python -c++ ETPython.i

# Compile the wrapper to object code (adjust Python paths to match your setup)
g++ -c -fPIC ETPython_wrap.cxx -I/Library/Frameworks/Python.framework/Versions/3.11/include/python3.11

# Link into a shared library, adding the Foundation framework
g++ -dynamiclib -o _ETPython.so ETPython_wrap.o -framework Foundation -L/Library/Frameworks/Python.framework/Versions/3.11/lib -lpython3.11

The key addition here is -framework Foundation — this tells the linker to include the necessary symbols from Apple's framework, including _NSLog.

Step 2: Fix Terminal Environment for Module Discovery #

Even after fixing the linking, you need to ensure Python can find your module in the terminal without hacky workarounds. Note that os.system('export PYTHONPATH=...') doesn't affect the current Python process (it only modifies a temporary subshell), which is why that line didn't help your terminal script run.

Temporary Terminal Fix #

Set the PYTHONPATH directly in your terminal session before running the script:

# For bash/zsh
export PYTHONPATH="/path/to/your/module/directory:$PYTHONPATH"
python3 sample.py

Or run it in one line to avoid modifying your session's environment permanently:

PYTHONPATH="/path/to/your/module/directory" python3 sample.py

Persistent Terminal Fix #

If you want this path to be available in all terminal sessions, add the export line to your shell's config file:

• For bash: ~/.bashrc or ~/.bash_profile
• For zsh: ~/.zshrc
• For fish: ~/.config/fish/config.fish

Step 3: Verify the Fix #

1. Recompile the shared library with the -framework Foundation flag as shown.
2. In your terminal, either navigate to the module directory or set PYTHONPATH correctly.
3. Run python3 sample.py — the _NSLog error should disappear, and the module should import successfully.

内容的提问来源于stack exchange，提问作者Oleksii Tiurin