What does not
step-by-step run/test project
What was not tested
work with database, OpenGL-projects
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Mandriva 2006||Jul 25 2005||0.9.39.||Yes||Yes||Silver||an anonymous user|
|Show||Debian GNU/Linux Unstable "Sid"||May 07 2007||0.9.31.||Yes||Yes||Gold||an anonymous user|
|Current||Fedora Core 6||Apr 10 2007||0.9.29.||Yes||Yes||Gold||an anonymous user|
|Show||Ubuntu 6.06 "Dapper" i386 (+ variants like Kubuntu)||Oct 03 2006||0.9.22.||Yes||Yes||Silver||an anonymous user|
|Show||Ubuntu 6.06 "Dapper" i386 (+ variants like Kubuntu)||May 10 2006||0.9.12.||Yes||Yes||Bronze||an anonymous user|
Outdated instructions from 2001
[description originally by tegel at a site named dubaron.com]
Originally Tested with: RedHat 7, win98se image, wine20010418-1, Delphi5 Professional UK.
How to use delphi 5 withÂ wine, and create native win32 programs on your unix box:
wine is perfectly able to run delphi 5, except for the borland debugger.
1. Make sure you have (a mirror of) a complete windows(9x) installation to use with wine.
2. If delphi 5 is not yet installed, install it by running the setup from the cd
. Everything on the setup should work fine (entering key code and so on), except for the last part. this is "normal", you probably won't get notified that setup was finished.
If delphi 5 was installed already, you might want to re-run the install within wine, but maybe it\'s not necessary.
3. Now check if stuff starts, by going to the "c:\\program files\\borland\\delphi5\\bin\" directory: >cd "~/wine/w98/program files/borland/delphi5/bin\" and starting
delphi: >wine delphi32.exe it can take a while, but you should see the splash screen and delphi5 should start up :))
Most likely (my case) delphi can\'t find any of it\'s registry settings. You\'ll easily notice, since the component pallete is missing... If you take a closer lookto all menu's, you'll probably see that a lot of information, path's and so on, is missing.
What we need to do is configure delphi by itself: Steps (not necessarely in this order):
-disable integrated debugging (very important, elsewise delphi will crash when running a compiled app):
Main menu => tools => Debugger options => Integrated debugging =>; Uncheck.
-now make sure delphi finds it's libraries:
main menu =>; tools =>; environment options => tabsheet 'library' => with library path add your "c:\\program files\\borland\\delphi5\\lib\" directory and the "c:\\windows\\system\" directory (c:\\winnt\\system32 with nt).
-install the design time components:
main menu => Component => Install Packages => Add now go to your "program files\\borland\\delphi5\\bin\" directory and pick the file "dclbde50.bpl" As soon as you do this you'll see the usual components appear :))
-make sure delphi has write access on the filesystem.
If you have done all these steps, do from within delphi: main menu - file - new application, and press F9 (run).
If all went fine, this newly created app should run! If not, make sure delphi gots write access! or force output directorys at your environment settings to point at a directory with write access.
Before you go build software:
- when saving a project, especially the first time, enter the .dpr extension explicitely within the savedialog box: projectname.dpr. If you omit this .dpr, delphi will not correctly reload the project.
This is only necessary with project files, not with .pas files!
-read the above sentence again to avoid wasting your time thinking why you can see your code but can't see your forms after reloading a project.
- if your app hangs, you'll have a tough time finding the right wine process, in which case you might have to close all wine apps (and programming is debugging). so double-check your code for endless loops and so before running, since you'll have to work without debugger.
-found some problems with 'ole containers' and other stuff, so don't expect all your existing programs to run immediately.
Note on the debugger: If somebody knows how to get the debugger up :)) i tried to regsvr32 the borland debugger dll, with no luck (placed in "program files\\common files\\borland shared\\debugger\\bordbk50.dll") with "wine regsvr32 bordbk50.dll", it then _is_ registered (and replaces drwatson) but it will _not_ run, which in fact sounds quite logical to me ;)