Skip to content

Latest commit

 

History

History
45 lines (30 loc) · 2.3 KB

building.md

File metadata and controls

45 lines (30 loc) · 2.3 KB
Raw

Building IronPython2

To build IronPython2 you will need the .NET SDK (minimum 4.5), a .NET Core SDK (minimum 3.1) and if building on Linux/macOS you will need Mono.

See Getting the Sources for information on getting the source for IronPython2.

Building from Visual Studio

Visual Studio 16.4(2019) or above is required to build IronPython2

  • Open c:\path\to\ironpython2\IronPython.sln solution file
  • Select the configuration options (Release,Debug, etc)
  • Press Ctrl+Shift+B or F6 to build the solution

Building from the command line

IronPython2 uses PowerShell to run the build and testing from the command line. You can either use a PowerShell directly, or prefix the commands below with powershell on Windows, or pwsh on Linux/macOS.

On Linux/macOS you will need to install PowerShell

Change the working directory to the path where you cloned the sources and run .\make.ps1

By default, with no options, make.ps1 will build Release mode binaries. If you would like to build debug binaries, you can run .\make.ps1 debug

Other options available for make.ps1 are

-configuration (debug/release)   The configuration to build for
-platform (x86/x64)              The platform to use in running tests
-runIgnored                      Run tests that are marked as ignored in the .ini manifests
-frameworks                      A comma separated list of frameworks to run tests for 
                                 (use nomenclature as is used in msbuild files for TargetFrameworks)

There are also other targets available for use with packaging and testing, most come in debug and release (default) versions, such as package-debug and package

package                         Creates packages supported by the current platform
stage                           Stages files ready for packaging
test-*                          Runs tests from `all` categories, `ironpython` specific tests, 
                                `cpython` tests from the C Python stdlib test suite, `smoke` a small
                                set of tests

If the build is successful the binaries are stored in ironpython2/bin/{ConfigurationName}/{Framework}