tsai
/
mathnet-numerics
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Math.NET Numerics
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1690 Commits
25 Branches
121 Tags
187 MiB
 
 
 
Tree: 0bf67ea4a4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0bf67ea4a4'
${ noResults }
mathnet-numerics/build
Christoph Ruegg 41a6639694
Build: drop legacy NuGet packaging build scripts 		12 years ago
..
FSharp.Formatting Docs: Turn F# Sample project into documentation (using FSharp.Literate/Formatting) 13 years ago
MSBuild.Community.Tasks.v1.2.0.306 NuGet Build 15 years ago
MSBuild.ExtensionPack.4.0.2.0 added misssing IndexedEnumerator tests and MSBuild Extensions 15 years ago
TeamCity Build: use semver assembly version for F# version patching 13 years ago
.gitignore build: creates base release file 16 years ago
License.txt updated license and doc generation info 15 years ago
MathNet.Numerics.nuspec Build: drop legacy NuGet packaging build scripts 12 years ago
README.md Rename markdown files to md-extension 13 years ago
packages.config Build: drop legacy MsBuild-integrated NuGet package-restore 12 years ago

README.md

Building Math.NET Numerics

Managed

The Math.NET Numerics solution is structured such that it is best to compile the whole solution (MathNet.Numerics.sln) directly in VisualStudio or by MsBuild.

All artifacts will be placed in a generated "out" directory in the solution root, structured as follows:

/lib/Net40: Binaries for .Net 4.0 /lib/SL4: Binaries for Silverlight 4

/debug/Net40: Debug Build for .Net 4.0 /debug/SL4: Debug Build for Silverlight 4

/test/Net40: Unit Tests for .Net 4.0 /test/debug/Net40: Debug Build Unit Tests for .Net 4.0

Windows Phone 7 builds will likely be added as "WP" subdirectories. Note that there are currently only unit tests for .Net 4.0 builds available.

Native Bindings

TODO

Continuous Integration

We use TeamCity both for continuous integration and release builds & deployments, the configuration and scripts are located in this folder and subfolders