view doc/README.Windows @ 358:30aae7371373

- extended signature with calling convention mode switches for fastcall (gnu), default, cdecl, stdcall, arm (arm), arm (thumb), syscall - made formatted call (dcV?{Call,Arg}F) interface use those calling convention mode signature specifications to begin with - extended callf testcode with one standard and one vararg call to test those cc mode switches
author Tassilo Philipp
date Mon, 13 Apr 2020 15:12:01 +0200
parents 3e629dc19168
children 451299d50c1a
line wrap: on
line source

Bulding DynCall on Windows
==========================


Build using buildsys/nmake and MS Visual Studio Tools:
------------------------------------------------------

  32-bit:
    vcvarsall.bat x86
    .\configure.bat /target-x86
    nmake /f Nmakefile

  64-bit:
    vcvarsall.bat amd64
    .\configure.bat /target-x64
    nmake /f Nmakefile

  Build/run tests:
    cd test
    nmake /f Nmakefile
    
    NOTE: if you encounter 'python'/'lua' not found messages (which is 
     executed mistakenly for re-generation of test C code)
     timestamps are wrong; workaround: run "svn revert -R ." several times.

Build using buildsys/gmake and MinGW or Cygwin:
-----------------------------------------------

  32-bit:
    .\configure.bat /target-x86 /tool-gcc
    make

  64-bit:
    .\configure.bat /target-x64 /tool-gcc
    make


Build using Makefile.embedded and MinGW or Cygwin:
--------------------------------------------------

    > mingw32-make -f Makefile.embedded
    $ make -f Makefile.embedded CC=gcc


Build using CMake and Nmake:
----------------------------

  Put the appropriate tool-chain in path (32 or 64-bit version of MSVC), then:
  
    cmake -G "NMake Makefiles" %DYNCALL_SOURCE_DIR%
    nmake


Build using CMake and Visual Studio:
------------------------------------
 
  32-bit:
    cmake .
    open DynCall.sln

  BROKEN: SAFE EH.

  BROKEN: Rules to assemble MASM files are still missing.