From: daz Date: 2003-07-05T21:24:43+09:00 Subject: Re: where to post: problem compiling ruby1.8 with borland c 5.5 "Pe�a, Botp" wrote: > KONTRA Gergely [mailto:kgergely@mlabdial.hit.bme.hu] wrote: > > > > This makes no sense. You should read the readme.txt in > > > \borland\bcc55. > > Damnit, thx, I hoped the installer'd done it ;( > > > > Everything went fine :) > > -- > > if you don't mind, can you post your complete steps? I'd like to compile it > using borland, too (found out late that it's free, and ms vc is too > expensive & heavy for me). > > > +-[ Kontra, Gergely PhD student Room IB113 > > kind regards -botp > Follow Eban's words from http://www.ruby-talk.org/75066 "ruby-1.8.0-source_tarball"\bcc32\README.bcc32 covers the rest well. It doesn't mention that you need byacc - (thanks to Yura for this) - http://prdownloads.sourceforge.net/gnuwin32/byacc-1.9-bin.zip?download (You don't need the docs .. it just happens) - which will be called by the Makefile, so the .exe files need to be in your %PATH%. If you already have bcc55\bin in the execution path, hey, why not drop the two .exe files in there unless you want to do things the right way ,) I was expecting that http://unxutils.sourceforge.net/UnxUtils.zip might be required, so I had these loaded. I don't think they are used, though. Set the drive: cd to your source directory (change create a 'build' directory under it (stick to the bccwin32 name) cd into this * new * dir. Then run configure.bat exactly as shown on the last line below. D: cd D:\ruby\SOURCE_CODE\ruby-1.8.0-p3 md bccwin32 cd bccwin32 REM ONLY ONCE (wipes \bcc32\Makefile) ...\bcc32\configure configure.bat looks as scary as hell but don't worry, do it now. Any customisation can be done next by modifying the Makefile which has just been created. Edit ruby-1.8.0-p3\bccwin32\Makefile using your favourite editor. (Don't worry about any blank junk lines - tidy up if you want to) Add a penultimate line to include your customisation which is TODO: - filename isn't important here. !include $(srcdir)bcc32/MakeX86.txt !include $(srcdir)bcc32/Makefile.sub TODO now: - create MakeX86.txt in the same dir. as Makefile.sub, not the build dir. MakeX86.txt ... smth like ??? #===---------------------===# PROCESSOR_ARCHITECTURE = i586 PROCESSOR_LEVEL = 5 DESTDIR = $(srcdir)rubyX86 # <---- or whatever --- # #===---------------------===# # starts comment in Makefile You could just add those lines to the Makefile instead of the new !include. Your choice. DESTDIR will be the install directory and a tree bearing an abundance of fruit will grow here with far more than you ever wished for; even curses (whatever that is). I ran the make process(es) from a batch file under SciTE. @echo off D: cd D:\ruby\SOURCE_CODE\ruby-1.8.0-p3\bccwin32 make (Modifying the last line each time) You need to use something that captures the output, otherwise you won't know what's going on. When Borland 'make' is called, this ensures that the current directory is set correctly. You can't just double-click on a file and expect things to be set OK ! The first 'make' compiles Mini-Me ruby. 'make test' runs Rubicon (is it Rubicon or is that smth else ?) 'make install' grows "The Tree" ... a spectacular event for a Windows user and as dull as ditch-water for Posix people who did the same thing yesterday and the day before. ===== First step is to give away all your personal details in exchange for the occasional newsletter - never had spam. http://www.borland.com/downloads/freecompiler This is NOT a GUI IDE, it's the same compiler as used in earlier BC++Builder packages (BCB4 ?)- it's command line only but it's fairly automatic once you're set up and you remember to set the current directory. Licensing for deployment of your own programs is very relaxed. A few GUI's are being developed for it ... e.g. http://www.fifsoft.com/relo/ which also handles ... www.mingw.org (GNU compiler+ on Windows) Many thanks to team-ruby who put this whole build process together. daz -- This information is guaranteed 0.00% accurate (or better)