I've got it working now.<br><br>Thanks for all your help :).<br>Turns out I have to set a variable PKG_CONFIG_PATH in .bash_profile that includes the path which has the mono.pc file in it. I don't have to edit anything anymore and it compiles <br>
<br>Thanks<br>Ivan<br><br><div class="gmail_quote">On Feb 5, 2008 8:57 AM, Ivan Porto Carrero <<a href="mailto:ivan@flanders.co.nz">ivan@flanders.co.nz</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks guys, I got it to build.<br>I do feel slightly dirty because it's somewhat hacky. (I'm very, very new to OSX) but I edited the Rakefil and set the libdir specifically there<br><br>FRAMEWORK_DIR = '/opt/local/mono/lib/mono/2.0/' #Pathname.new(libdir) + 'mono' + '2.0'<br>
<br>I'm not entirely happy with this solution and it probably has something to do with an environment variable not being set correctly, but at least i know it can be done now and eventually I'll get it so that the standard rake file suffices.<br>
<br>I've seen that the command 'pkg-config --variable=libdir mono' doesn't return anything, which may be the cause :)<br><br>Cheers<br><font color="#888888">Ivan</font><div><div></div><div class="Wj3C7c">
<br><br><div class="gmail_quote">On Feb 5, 2008 2:39 AM, M. David Peterson <<a href="mailto:m.david@xmlhacker.com" target="_blank">m.david@xmlhacker.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>On Sun, 03 Feb 2008 13:14:28 -0700, Ivan Porto Carrero<br><<a href="mailto:ivan@flanders.co.nz" target="_blank">ivan@flanders.co.nz</a>> wrote:<br>
<br>> ok .. I'll keep trying then until I get a working mono version. Haven't<br>> done much testing with mono but I did run the minimal test suite before<br>> installing.<br>> If I compile on windows and use the binaries there is no problem.<br>
<br></div>Are you compiling with both --with-preview=yes and --with-moonlight=yes ?<br><br>Actually, I think they both are set to yet by default, but if you're<br>building from SVN you'll need to checkout not only the mono directory but<br>
olive, moon, mcs, and (possibly) gtk-sharp as well. You've already got<br>mono checked out, so if you enter the same directory that the mono<br>directory is contained in and run,<br><br>svn co<br>svn://anonsvn.mono-<a href="http://project.com/source/trunk/%7Bmcs,moon,olive,gtk-sharp%7D" target="_blank">project.com/source/trunk/{mcs,moon,olive,gtk-sharp}</a><br>
<br>... to then svn up mono you can then enter the mono directory and run,<br><br>./autogen.sh --with-preview=yes --with-moonlight=yes [additional options<br>(such as --prefix)]<br><br>NOTE: I realize I mentioned that I believe both of these values are yes by<br>
default, but it doesn't hurt so it's worth adding them just in case.<br><br>If that script finishes without erroring out then run,<br><br>make; sudo make install<br><br>If it does error out there's a good chance it's going to be one of several<br>
things,<br><br>1) The existing DMG-based installation is getting in the way. I would<br>move /Library/Frameworks/Mono.framework (if you don't see it there, try<br>~/Library/Frameworks/Mono.framework) to another directory to ensure you're<br>
not running into a problem with the build process linking against the<br>wrong libraries.<br>2) The generated ./configure file will have a few lines that autotools<br>will claim to be invalid syntax. If you see this problem, just open the<br>
./configure file, go to the specified line, and comment it out.<br>IMPORTANT!: Don't rerun ./autogen.sh at this point. It will write over<br>the previous generated ./configure file and cause the same error to occur.<br>
<br>At this stage of the game you'll then want to run,<br><br>./configure --with-preview=yes --with-moonlight=yes [additional options<br>(such as --prefix)]; make; sudo make install<br><br>At this point you're system should be completely up-to-date with all of<br>
the latest code that is specific to the needs of the DLR and DLR-based<br>languages. That doesn't mean it's guaranteed to compile and work, but<br>I've yet to find a situation unrelated to System.Windows.Forms that didn't<br>
work on OS X if it worked on Linux. It sometimes takes a bit of hacking<br>the build process, but it usually works out in the end. :D<br><br>That said, given the IronRuby and the DLR are moving targets, there's no<br>
guarantee you're not going to run into issues. But in my own experience,<br>the Mono team places an extremely high importance on bugs related to the<br>Iron* projects and the DLR. Often times there's a fix checked into SVN<br>
within a few hours of filing the report.<br><br>Hope this helps!<br><br>--<br>/M:D<br><font color="#888888"><br>M. David Peterson<br>Co-Founder & Chief Architect, 3rd&Urban, LLC<br>Email: <a href="mailto:m.david@3rdandUrban.com" target="_blank">m.david@3rdandUrban.com</a> | <a href="mailto:m.david@amp.fm" target="_blank">m.david@amp.fm</a><br>
Mobile: (206) 418-9027<br><a href="http://3rdandUrban.com" target="_blank">http://3rdandUrban.com</a> | <a href="http://amp.fm" target="_blank">http://amp.fm</a> |<br><a href="http://www.oreillynet.com/pub/au/2354" target="_blank">http://www.oreillynet.com/pub/au/2354</a><br>
</font><div><div></div><div>_______________________________________________<br>Ironruby-core mailing list<br><a href="mailto:Ironruby-core@rubyforge.org" target="_blank">Ironruby-core@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/ironruby-core" target="_blank">http://rubyforge.org/mailman/listinfo/ironruby-core</a><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>