Paul Moore added the comment: Worked fine for me:
>cl .\pyc.c /I $env:LOCALAPPDATA\Programs\Python\Python36\include >$env:LOCALAPPDATA\Programs\Python\Python36\libs\python36.lib Microsoft (R) C/C++ Optimizing Compiler Version 19.00.24213.1 for x64 Copyright (C) Microsoft Corporation. All rights reserved. pyc.c Microsoft (R) Incremental Linker Version 14.00.24213.1 Copyright (C) Microsoft Corporation. All rights reserved. /out:pyc.exe pyc.obj ...\Programs\Python\Python36\libs\python36.lib >.\pyc.exe Today is Mon Jun 5 15:27:45 2017 So it doesn't look like the problem is with the code, so much as with how you've done the build. The problem here is that there are so many possibilities for C compilation environments, that there's simply no way we could give a "this is how you set up to build an embedding application". If you have specific suggestions for how to improve the documentation, a patch would be welcome. But in the absence of specifics, I don't think there's anything actionable in this report. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30574> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
