From: Pedro Lamarão (pedro.lamarao_at_[hidden])
Date: 2006-03-10 08:23:46
Reece Dunn escreveu:
> I tried to get .net support working and managed to get a simple console app running using either C#, J# or VB.NET. However, I haven't looked at this for some time now. Also I haven't looked at Pedro's patch yet, so I can't comment.
> One thing I will note is that the C# support should be separate from the msvc toolset
> as they are two different compilers tagretting different languages.
> My idea is that you would have a _net.jam (or more preferable a
dotnet.jam file) that
> registers the intermediate types and then a cs.jam, js.jam and
vbnet.jam that provide support for the C#,
> J# and VB.NET languages. I am looking at adding support in msvc for
targetting the CLI framework
> (either the older managed C++ or the new, proposed "C++/CLI") -- this
could then pull in the CLI
> related features (assembly includes, etc.).
I agree with this approach; I worked a quick hack to experiment with our
After a day of experiment, I feel a dotnet.jam similar to msvc.jam for
the .NET SDK could work very well; the paths for toolsets in
/WINNT/Microsoft.NET/Framework/ are very predictable. This is my current
attempt. At the end of the day I'll have proper feature support.
Then, with something similar for Mono, we escape Windows.
As for "managed C++", <cxxflags>/CLR did the trick for us.
-- Pedro Lamarão
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk