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.
496 Commits
25 Branches
121 Tags
187 MiB
 
 
 
Tree: 07162fb76f
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '07162fb76f'
${ noResults }
mathnet-numerics/build
Marcus Cuda 64321c247c
ci: updated t4 bat file to include MKL.XXX.Common.tt 		16 years ago
..
CodePlexApi build: adding CodePlex API DLL so we can upload new releases from msbuild 17 years ago
MSBuild_Extension_Pack_3.5.5 updated version of MSBuild Extension Pack 17 years ago
TeamCity ci: updated t4 bat file to include MKL.XXX.Common.tt 16 years ago
.gitignore build: creates base release file 17 years ago
build.proj fixed a complex ToString bugs and lowered the accuracy on some of the single precision tests that were failing on x64 16 years ago
mathnet-numerics.shfbproj build: update SHFB paths to match new build server (temp hack, need dynamic paths) 17 years ago
readme.mkd Ci: make projects build to a common out folder with a decent folder structure out of the box 16 years ago
t4.bat trying get T4 running on Windows Server 2003 17 years ago

readme.mkd

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