How can I compile python c extension for the Window 10 Maya 2017 python?












0














After going through quite a pain getting my python setup.py to work with setuptools and the dedicated microsoft VC (Microsoft Visual C++ Compiler Package for Python 2.7) and succesfully compiling my extension on windows 10 it turns out the Maya 2017 included python executable (mayapy) is compiled with a different version, see below.



c:>python
Python 2.7.1 (r271:86832, Nov 27 2010, 17:19:03) [MSC v.1500 64 bit (AMD64)] on win32



c:>"Program FilesAutodeskMaya2017binmayapy.exe"
Python 2.7.11 (default, Dec 21 2015, 22:48:54) [MSC v.1700 64 bit (AMD64)] on win32



I have Visual Studio 12 installed as well and that seems to be the right compiler version.



But how can I tell setuptools to use that version?



Thanks










share|improve this question



























    0














    After going through quite a pain getting my python setup.py to work with setuptools and the dedicated microsoft VC (Microsoft Visual C++ Compiler Package for Python 2.7) and succesfully compiling my extension on windows 10 it turns out the Maya 2017 included python executable (mayapy) is compiled with a different version, see below.



    c:>python
    Python 2.7.1 (r271:86832, Nov 27 2010, 17:19:03) [MSC v.1500 64 bit (AMD64)] on win32



    c:>"Program FilesAutodeskMaya2017binmayapy.exe"
    Python 2.7.11 (default, Dec 21 2015, 22:48:54) [MSC v.1700 64 bit (AMD64)] on win32



    I have Visual Studio 12 installed as well and that seems to be the right compiler version.



    But how can I tell setuptools to use that version?



    Thanks










    share|improve this question

























      0












      0








      0







      After going through quite a pain getting my python setup.py to work with setuptools and the dedicated microsoft VC (Microsoft Visual C++ Compiler Package for Python 2.7) and succesfully compiling my extension on windows 10 it turns out the Maya 2017 included python executable (mayapy) is compiled with a different version, see below.



      c:>python
      Python 2.7.1 (r271:86832, Nov 27 2010, 17:19:03) [MSC v.1500 64 bit (AMD64)] on win32



      c:>"Program FilesAutodeskMaya2017binmayapy.exe"
      Python 2.7.11 (default, Dec 21 2015, 22:48:54) [MSC v.1700 64 bit (AMD64)] on win32



      I have Visual Studio 12 installed as well and that seems to be the right compiler version.



      But how can I tell setuptools to use that version?



      Thanks










      share|improve this question













      After going through quite a pain getting my python setup.py to work with setuptools and the dedicated microsoft VC (Microsoft Visual C++ Compiler Package for Python 2.7) and succesfully compiling my extension on windows 10 it turns out the Maya 2017 included python executable (mayapy) is compiled with a different version, see below.



      c:>python
      Python 2.7.1 (r271:86832, Nov 27 2010, 17:19:03) [MSC v.1500 64 bit (AMD64)] on win32



      c:>"Program FilesAutodeskMaya2017binmayapy.exe"
      Python 2.7.11 (default, Dec 21 2015, 22:48:54) [MSC v.1700 64 bit (AMD64)] on win32



      I have Visual Studio 12 installed as well and that seems to be the right compiler version.



      But how can I tell setuptools to use that version?



      Thanks







      python c windows maya






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 19 '18 at 20:39









      Paul BootsPaul Boots

      163




      163
























          1 Answer
          1






          active

          oldest

          votes


















          0














          The quick and dirty way is to use to compile the required DLL on the command line using the Command Prompt for the VS2012 x64 Native Tools. The version that matches the mayapy.exe in Maya 2017.



          To compile your c code use cl. You may need to point to the Python 2.7 include files using /I.




          cl /DL /I ..include /I C:Python27include




          Because the linker might have trouble finding the 'python27.lib' you can link manually as well using /LIBPATH to point to the Python 2.7 libs directory.




          link /DLL /LIBPATH:C:Python27libs *.obj




          This will give you a DLL and intermediate files matching the compiler for mayapy.exe.



          The dirty part.
          Build the extension using python setup.py build. This will give you a module that will import in the regular python interpreter. Remove the 'lib*' directory in the 'build' folder. Copy the '.obj', '.exp' and the dll to the temp folder in your build folder, something like 'temp.win-amd64-2.7Release\src'.



          Then run python setup.py build again.
          Dirty yes, Quick, once you know what to do...






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53382295%2fhow-can-i-compile-python-c-extension-for-the-window-10-maya-2017-python%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            The quick and dirty way is to use to compile the required DLL on the command line using the Command Prompt for the VS2012 x64 Native Tools. The version that matches the mayapy.exe in Maya 2017.



            To compile your c code use cl. You may need to point to the Python 2.7 include files using /I.




            cl /DL /I ..include /I C:Python27include




            Because the linker might have trouble finding the 'python27.lib' you can link manually as well using /LIBPATH to point to the Python 2.7 libs directory.




            link /DLL /LIBPATH:C:Python27libs *.obj




            This will give you a DLL and intermediate files matching the compiler for mayapy.exe.



            The dirty part.
            Build the extension using python setup.py build. This will give you a module that will import in the regular python interpreter. Remove the 'lib*' directory in the 'build' folder. Copy the '.obj', '.exp' and the dll to the temp folder in your build folder, something like 'temp.win-amd64-2.7Release\src'.



            Then run python setup.py build again.
            Dirty yes, Quick, once you know what to do...






            share|improve this answer


























              0














              The quick and dirty way is to use to compile the required DLL on the command line using the Command Prompt for the VS2012 x64 Native Tools. The version that matches the mayapy.exe in Maya 2017.



              To compile your c code use cl. You may need to point to the Python 2.7 include files using /I.




              cl /DL /I ..include /I C:Python27include




              Because the linker might have trouble finding the 'python27.lib' you can link manually as well using /LIBPATH to point to the Python 2.7 libs directory.




              link /DLL /LIBPATH:C:Python27libs *.obj




              This will give you a DLL and intermediate files matching the compiler for mayapy.exe.



              The dirty part.
              Build the extension using python setup.py build. This will give you a module that will import in the regular python interpreter. Remove the 'lib*' directory in the 'build' folder. Copy the '.obj', '.exp' and the dll to the temp folder in your build folder, something like 'temp.win-amd64-2.7Release\src'.



              Then run python setup.py build again.
              Dirty yes, Quick, once you know what to do...






              share|improve this answer
























                0












                0








                0






                The quick and dirty way is to use to compile the required DLL on the command line using the Command Prompt for the VS2012 x64 Native Tools. The version that matches the mayapy.exe in Maya 2017.



                To compile your c code use cl. You may need to point to the Python 2.7 include files using /I.




                cl /DL /I ..include /I C:Python27include




                Because the linker might have trouble finding the 'python27.lib' you can link manually as well using /LIBPATH to point to the Python 2.7 libs directory.




                link /DLL /LIBPATH:C:Python27libs *.obj




                This will give you a DLL and intermediate files matching the compiler for mayapy.exe.



                The dirty part.
                Build the extension using python setup.py build. This will give you a module that will import in the regular python interpreter. Remove the 'lib*' directory in the 'build' folder. Copy the '.obj', '.exp' and the dll to the temp folder in your build folder, something like 'temp.win-amd64-2.7Release\src'.



                Then run python setup.py build again.
                Dirty yes, Quick, once you know what to do...






                share|improve this answer












                The quick and dirty way is to use to compile the required DLL on the command line using the Command Prompt for the VS2012 x64 Native Tools. The version that matches the mayapy.exe in Maya 2017.



                To compile your c code use cl. You may need to point to the Python 2.7 include files using /I.




                cl /DL /I ..include /I C:Python27include




                Because the linker might have trouble finding the 'python27.lib' you can link manually as well using /LIBPATH to point to the Python 2.7 libs directory.




                link /DLL /LIBPATH:C:Python27libs *.obj




                This will give you a DLL and intermediate files matching the compiler for mayapy.exe.



                The dirty part.
                Build the extension using python setup.py build. This will give you a module that will import in the regular python interpreter. Remove the 'lib*' directory in the 'build' folder. Copy the '.obj', '.exp' and the dll to the temp folder in your build folder, something like 'temp.win-amd64-2.7Release\src'.



                Then run python setup.py build again.
                Dirty yes, Quick, once you know what to do...







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 22 '18 at 23:22









                Paul BootsPaul Boots

                163




                163






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53382295%2fhow-can-i-compile-python-c-extension-for-the-window-10-maya-2017-python%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    'app-layout' is not a known element: how to share Component with different Modules

                    android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

                    WPF add header to Image with URL pettitions [duplicate]