Projekte, die mit Delphi 6 Personal erstellt wurden, koennen nicht direkt in Kylix verwendet werden. In Delphi 6 Personal fehlen die CLX Komponenten (Cross Platform Development Library) und nur VCL wird unterstuetzt:
http://www.borland.com/delphi/pdf/del6_feamatrix.pdf
Mit recht viel Aufwand kann trotzdem ein Projekt konvertiert werden, wie aus der Hilfe zu Delphi 7 Professional ersichtlich ist.
Hier koennen die Hilfedateien heruntergeladen werden:
http://info.borland.com/techpubs/delphi/
Du wirst aber wahrscheinlich nur in den Professional/Enterprise Hilfen die entsprechenden Funktionen beschrieben finden. Ausserdem bin ich mir nicht sicher, ob das die kompletten Hilfedateien sind oder nur Updates.
Zumindest bei Delphi 7 Professional ist der komplette Konvertierprozess beschrieben.
Hier kurz aus der Hilfe zitiert:
[--- SNIP ---]
You can develop cross-platform 32-bit applications that run on both the Windows and Linux operating systems. Cross-platform applications use CLX components from the Borland Component Library for Cross-Platform (CLX) and don't make any operating system-specific API calls.
Weiter:
If you are porting a VCL application to Linux that you want to run on both Windows and Linux, you may need to modify your code or use conditional compiler directives to indicate sections of the code that apply specifically to Windows or Linux.
To modify your VCL application so that it can run on Linux, follow these general steps:
1 In Windows, open the project containing the VCL application you want to change.
2 Rename your form files (.dfm) to cross-platform form files (.xfm). For example, rename unit1.dfm to unit1.xfm. Or add an $IFDEF compiler directive. An .xfm form file works on both Windows or Linux but a .dfm form only works on Windows.
Change {$R *.dfm} to {$R *.xfm} in the implementation section.
3 Change all uses clauses in your source file so they refer to the correct units in VisualCLX. (See Comparing WinCLX and VisualCLX units for information.)
For example, change the following uses clause:
uses Windows, Messages, SysUtils, Variants, Classes, Graphics, Controls, Forms, Dialogs, StdCtrls;
to the following:
uses SysUtils, Types, Classes, QGraphics, QControls, QForms, QDialogs, QStdCtrls;
4 Save the project and reopen it. Now the Component palette shows components that can be used in CLX applications.
Note
Some Windows-only nonvisual components can be used in cross-platform applications but only work in Windows cross-platforms applications. If you plan to compile your application on Linux as well, either do not use the nonvisual WinCLX components in your applications or use $IFDEFs to mark these sections of the code as Windows only. You cannot use the visual part of WinCLX with VisualCLX in the same application.
5 Rewrite any code that requires Windows dependencies by making the code more platform-independent. Do this using the runtime library routines and constants. (See Cross-platform database applications for information.)
6 Find equivalent functionality for features that are different on Linux. Use conditional compiler directives such as $IFDEFs (sparingly) to delimit Windows-specific information. (See Using conditional directives for information.)
For example, you can use conditional compiler directives for platform-specific code in your source files:
{$IFDEF MSWINDOWS}
IniFile.LoadfromFile('c:\x.txt');
{$ENDIF}
{$IFDEF LINUX}
IniFile.LoadfromFile('/home/name/x.txt');
{$ENDIF}
7 Search for references to pathnames in all the project files.
Pathnames in Linux use a forward slash / as a delimiter (such as /usr/lib) and files may be located in different directories on the Linux system. Use the PathDelim constant (in SysUtils) to specify the path delimiter that is appropriate for the system. Determine the correct location for any files on Linux.
Change references to drive letters (for example, C:\) and code that looks for drive letters by looking for a colon at position 2 in the string. Use the DriveDelim constant (in SysUtils) to specify the location in terms that are appropriate for the system.
In places where you specify multiple paths, change the path separator from semicolon ( ; ) to colon ( : ). Use the PathSep constant (in SysUtils) to specify the path separator that is appropriate for the system.
Because file names are case-sensitive in Linux, make sure that your application doesn't change the case of file names or assume a certain case.
See Programming differences on Linux.
