-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nimporter ignores nim.cfg #43
Comments
@mhechthz can you post the nim.cfg? |
It's the default nim.cfg, with the only change
How can I be sure, that this config file from Nim installation directory is really used? I set the PATH to NimInstallDir\bin. EDIT: It seems that LLVM is using MSVC++ during linking. That's probably the reason why I see this running. Nevertheless, it doesn't work |
Hello @mhechthz I was able to get both of the code snippets to work on my Windows 10 machine using MSVC. Nimporter can't change Nim's behavior for supporting However, you mentioned that "Visual Studio" (the graphical application) starts up when you run the Python example above? |
Also, Nimporter will tell Nim to use MSVC only if Python was compiled with MSVC. You can tell if Python is compiled with MSVC by running this in a Python shell: >>> import sys; sys.version
'3.7.3 (v3.7.3:ef4ec6ed12, Mar 25 2019, 22:22:05) [MSC v.1916 64 bit (AMD64)]' The "MSC" in the square brackets is for MSVC. If "MSC" is not in |
If you need to explicitly control 100% of all flags Nimporter passes to Nim, you can use a switches.py script. |
Closing for now |
Hi,
I'm totally new to Nim and nimporter and tried to build a little test application. I changed Nim to use clang, which is compatible with CPython on Windows 10. Nim file:
Python file:
Running the nim-file using Nim works perfectly. Compiling to library (nimpy only) and importing to Python also works perfectly.
Running the Python program "hangs" the execution and while trying to start Visual C++. Both files are in the same directory, i.e. there is no directory structure.
What is wrong here?
The text was updated successfully, but these errors were encountered: