Having multiple building systems is counterproductive, it's hard to maintain all of them.
Is cmake using xbuild to buil the dlls or does it all the file linking by itself? On Wed, Nov 3, 2010 at 11:54 AM, Alistair Bush <ali_b...@gentoo.org> wrote: > I have started playing around with cmake to see whether it could help out > iron* and dlr. I have therefore started implementing CMake makefiles to > build > the dlr (Runtime) part of ironruby, install those dlls into the gac and > generate *.pc files for them. I have tested it on mono-2.8 (requires > mono-2.8) > and am aware that windows .NET support is broken (but very possible) > > cmake also supports creating deb's and rpm's which will be done in the > future > hopefully. The potential is also there for it to generate csproj files > (already supports other VS file types) > > To play around with it > > git clone git://github.com/alistair/ironruby.git > mkdir build > mkdir install > cd build (out of tree builds, oh how I love them ) > cmake ../repo/Runtime/ > make > make DESTDIR=../install install > > > After this you should have > > install $ find > . > ./usr > ./usr/lib64 > ./usr/lib64/mono > ./usr/lib64/mono/Microsoft.Scripting.Metadata > > ./usr/lib64/mono/Microsoft.Scripting.Metadata/Microsoft.Scripting.Metadata.dll > ./usr/lib64/mono/Microsoft.Dynamic > ./usr/lib64/mono/Microsoft.Dynamic/Microsoft.Dynamic.dll > ./usr/lib64/mono/Microsoft.Scripting > ./usr/lib64/mono/Microsoft.Scripting/Microsoft.Scripting.dll > ./usr/lib64/mono/Microsoft.Scripting.Core > ./usr/lib64/mono/Microsoft.Scripting.Core/Microsoft.Scripting.Core.dll > ./usr/lib64/mono/gac > ./usr/lib64/mono/gac/Microsoft.Scripting.Metadata > > ./usr/lib64/mono/gac/Microsoft.Scripting.Metadata/1.1.0.10__7f709c5b713576e1 > > ./usr/lib64/mono/gac/Microsoft.Scripting.Metadata/1.1.0.10__7f709c5b713576e1/Microsoft.Scripting.Metadata.dll > ./usr/lib64/mono/gac/Microsoft.Dynamic > ./usr/lib64/mono/gac/Microsoft.Dynamic/1.1.0.10__7f709c5b713576e1 > > ./usr/lib64/mono/gac/Microsoft.Dynamic/1.1.0.10__7f709c5b713576e1/Microsoft.Dynamic.dll > ./usr/lib64/mono/gac/Microsoft.Scripting > ./usr/lib64/mono/gac/Microsoft.Scripting/1.1.0.10__7f709c5b713576e1 > > ./usr/lib64/mono/gac/Microsoft.Scripting/1.1.0.10__7f709c5b713576e1/Microsoft.Scripting.dll > ./usr/lib64/mono/gac/Microsoft.Scripting.Core > ./usr/lib64/mono/gac/Microsoft.Scripting.Core/1.1.0.10__7f709c5b713576e1 > > ./usr/lib64/mono/gac/Microsoft.Scripting.Core/1.1.0.10__7f709c5b713576e1/Microsoft.Scripting.Core.dll > ./usr/local > ./usr/local/lib > ./usr/local/lib/pkgconfig > ./usr/local/lib/pkgconfig/microsoft.scripting.metadata.pc > ./usr/local/lib/pkgconfig/microsoft.scripting.core.pc > ./usr/local/lib/pkgconfig/microsoft.dynamic.pc > ./usr/local/lib/pkgconfig/microsoft.scripting.pc > > still lots of work to do, but hopefully you enjoy. > > Alistair. > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core >
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
