We may use wget to download files from HTTP or FTP services in background without user intervention. wget supports resume and retry features as well.
Download a file
wget http://server/file
Download a file in background
wget -b http://server/file
Download a file in background and turn off Wgets Output
wget -b -q http://server/file
Download a file in background with infinite retrying
wget -b -t0 -q http://server/file
First, I thought all printers configure on CUPS as local raw printer should works for windows workstation as long as I use correct printer driver to render the printing image. The CUPS will just re-route the raw printing image received to the printer.
I have follow this rule to configure two other printers: Panasonic KX-1121 dot matrix printer and Samsung ML-1450 Laser Jet Printer. Both works flawlessly for years.
I receive a HP LaserJet 1020 printer last night and try to configure it for CUPS. The printer has only one USB port. I plug the printer to the Linux machine's USB port and CUPS detect the printer well. I then install the latest HP LaserJet 1020 printer downloaded from HP web site and configure the printer as usual. I send a test page to printer. CUPS receive the printing image and report print job completed successfully but the printer doesn't print anything. The printer doesn't feed the paper.
I thought it was printer's problem. To re-confirm the problem again, I attach the printer to my Windows Vista machine directly. It print perfectly.
I found some interesting things with HP LaserJet 1020 after Google for solutions.
As defined by HP:
The host-based software uses the computer's resources to process print commands and rasterizing data, taking advantage of the computer's memory and processing power. Host-Based printing is a cost-effective printing technology that enables printers to utilize the processing power and memory resources of the PC (or the Host). In comparison, PDL-based printers use the processor and memory resources of the printer.
It utilize the power and resources of PC to render the printing images. It print much faster than those PDL printer since newer computers process at much faster speeds than most PDL printers processors.
The disadvantages of Host-Based Printers is it no longer accept ASCII text directly from computer as all print images are generated by host operating system's print engine.
This however, is a good news as it reduce the manufacturing cost of the printer. It also doesn't seems to be a problem for my RAW printer for CUPS service.
The printer is one of the cost-reduced HP printers that requires a firmware download before it will operate. It means every time you switch on the printer, you need to send the firmware image to printer first before you start feeding the printing images. The HP LJ1020 doesn't has a flash ROM to persist the firmware permanently. This is the main reason why the printer works well when attach to windows vista machine but not Linux machine. The HP LJ1010 printer drivers for windows OS take care of the firmware uploading well.
You may only get the N series of HP 1000 printers that has flash ROM equipped for firmware. For example, HP LaserJet 1020n printer.
I only need foo2zjs to upload the firmware to printer when the HP LJ1020 first attach to my Linux box.
You may now start feeding the raw printing images from your windows workstation to HP Laser Jet 1020.
I start learn the concept of array in high school mathematic subject. The array has dimensions, 1D, 2D and so on. The first programming language BASIC I learned also has array. The concept of mathematic array and programming array match perfectly. However, there is always a memory restriction using array in 8-bits and 16-bits world.
I start ignore array after I learn object oriented programming and design patterns. There is always ready classes like TList or TCollection for me to use in OO world. The OOP concept has poisoned me for years that I should always coding in OO way. The TList class can do more than array and I almost forget that Object Pascal still has array.
I migrate my Delphi 2007 code to Delphi 2009 when it was launched. In the migration stage, the most headache part is unicode conversion. Due to several reasons below:
I will still stay in Delphi 2007 for a while before I am ready to release application compiled in Delphi 2009.
At this stage, I will revise all my code that aren't compatible with Delphi 2009 and amend it to compatible for both Delphi 2007 and Delphi 2009.
I have some classes perform Base16 and Base64 encoding. These classes using string to as internal storage. It become a problem in Delphi 2009 as it use WideChar (2 bytes) and the effect is avalanche as other part of source use the encoding classes. I revise the code and use TBytes (array of byte) as internal storage.
A new problem raise, the lack of solid array knowledge has slow down my day to day coding practice. My knowledge of array is still stay in high school. I re-study the array construct in Delphi documentation to strengthen my understanding about it. Some I already know but some don't. Below are the result of my study.
Static array has fixed memory allocated at compiled time. For example,
var A, B: array[1..10] of integer;
define A and B as byte array of 10 element.
To initialize a static array:
var C: array[1..3] of integer = (1, 2, 3);
As it name implied, the size of dynamic array is not fixed at compile time. It is determine at runtime. Thus, there are some operations distinct to static array:
var A: array of integer;
A is of type pointer to an array memory storage. Thus, when we apply any operation against dynamic array, always treat it as pointer to reduce any confusions for operation like FillChar or Move.
Use SetLength to allocate memory storage for dynamic array:
SetLength(A, 10)
A good news is the system will manage the dynamic array storage area. there is no need to free the storage size allocated via SetLength.
To initialize a dynamic array (undocumented feature):
type
TDynIntegerArray = array of integer;var C: TDynByteArray;
begin
C := TDynByteArray.Create(1, 2, 3, 4);
end;
Arrays are assignment-compatible only if they are of the same type. Because the Delphi language uses name-equivalence for types, the following code will not compile:
var A: array[1..10] of integer;
B: array[1..10] of integer;
C: array of integer;
D: array of integer;
begin
B := A;
D := C;
end;
To make it works, either do this:
var A, B: array[1..10] of integer;
C, D: array of integer;
begin
B := A;
D := C;
end;
or
type TIntegerArray = array[1..10] of integer;
TDynIntegerArray = array of integer;var A: TIntegerArray;
B: TIntegerArray;
C: TDynIntegerArray;
D: TDynIntegerArray;
begin
B := A;
D := C;
end;
As static arrays has pre-allocated memory storage, copy-on-write is not employed on static array assignment. In the above example, B will copy of all elements' value from A. Changing any value in B[i] will has no effect on A. A and B has 2 independent storage area.
Unlike static array, dynamic array reference is a pointer. Thus, B := A will make B point to A's storage area. The storage area for A is also storage area for B now. Changing value in A[i] will be reflected immediately on B[i] and vice versa. Both A and B share same storage area. To practice copy-on-write for dynamic array, use Copy function
B := Copy(A, 0, Length(A)):
It is not need to allocate storage for B using SetLength prior to Copy. Now A and B has two distinct storage area. Changing B[i] or A[i] do not affect each other.
Open Array is not static or dynamic array. It is use as parameters in procedures or functions.
Unfortunately, it has same syntax as dynamic array and always confuse us. Open array parameter must always declares as "array of <baseType>". If we declare a type for it, it is not an open array.
This is open array parameter:
procedure MyProc(A: array of integer);This is not open array parameter:
type
TIntegerArray = array of integer;
procedure MyProc(A: TIntegerArray);
begin
end;
Open array has several rules:
For example,
procedure MyProc(A: array of integer);
begin
WriteLn('SizeOf(A)=', SizeOf(A));
WriteLn('Length(A)=', Length(A));
end;
var A: array[0..9] of integer;
begin
MyProc(A);
end;
The output is
We can pass variable to open array parameter of a routine, it will be treated as a single element array:
var i: integer;
begin
MyProc(i);
end;
The output is
For simple construct, using array is efficient and easy. It consume less system resources than collection classes.
SizeOf and Length always confuse me. Some time both function return same result but not always. There are situations they have same behaviors but not always.
In Delphi 2009 documentation:
SizeOf
function SizeOf(X): Integer;
Returns the number of bytes occupied by a variable or type.
Length
function Length(S): Integer;
Returns the number of characters in a string or elements in an array.
For static array, the size of array is statically reserved by compiler. Thus, SizeOf know the total number of bytes allocated for the array.
Length will always behave as defined regardless of the element size of array, that is return the number of element in the array.
var A: array[0..9] of byte;
var B: array[0..9] of char;
Unlike static array, a variable reference dynamic array is of pointer type. Thus, apply SizeOf on a dynamic array point always return 4, that is same as SizeOf(Pointer) no matter how much memory allocated to the dynamic array at runtime.
Length as always, return the number of elements in array.
var A: array of byte; // or TBytes
begin
SetLength(A, 10);
end;
var C: array of char; // or TBytes
begin
SetLength(C, 10);
end;
Open array parameters allow arrays of different sizes to be passed to the same procedure or function. To define a routine with an open array parameter, use the syntax array of type (rather than array[X..Y] of type) in the parameter declaration. For example,
procedure MyProc(A: array of integer);
begin
WriteLn('SizeOf(A)=', SizeOf(A));
declares a procedure called MyProc that takes a integer array of any size.
We may pass either a static or dynamic array to MyProc but not limited to that.
Example 1: Dynamic array
var A: array of integer;
begin
SetLength(A, 10);
MyProc(A);
end;
The output is
Example 2: Static array
var A: array[0..9] of integer;
begin
MyProc(A);
end;
The output is
Example 3: Static array
begin
MyProc([0,1,2,3,4,5,6,7,8,9]);
end;
The output is
Example 4: Integer variable
Instead of an array, you can pass a variable of the open array parameter's base type. It will be treated as an array of length 1.
var i: integer;
begin
MyProc(i);
end;
The output is
Example 5: Open Array or Dynamic Array
It is easy to confuse about the array syntax. The syntax of open array parameters resembles that of dynamic array types, but they do not mean the same thing. If you declare a type identifier for an array, it will be treated as dynamic array:
type
TIntegerArray = array of integer;
procedure MyProc(A: TIntegerArray);
begin
WriteLn('SizeOf(A)=', SizeOf(A));
WriteLn('Length(A)=', Length(A));
end;
var A: TIntegerArray;
begin
SetLength(A, 10);
MyProc(A);
end;
The output is
Reference:
This compiler warning is commonly encounter in Delphi 2009. We should change all coding using characters set with CharInSet.
For example:
Delphi 2007: A in ['a', 'b']
Delphi 2009: CharInSet(A, ['a', 'b'])
However, doing such changes will make the code not compatible with Delphi 2007. We may construct a CharInSet function for Delphi 2007:
unit D2009_to_D2007;
interface
{$if CompilerVersion <= 18.5}
function CharInSet(C: AnsiChar; const CharSet: TSysCharSet): Boolean; inline;
{$ifend}
implementation
{$if CompilerVersion <= 18.5}
function CharInSet(C: AnsiChar; const CharSet: TSysCharSet): Boolean;
begin
Result := C in CharSet;
end;
{$ifend}
end.
The $if directive will restrict the code available for Delphi 2007 or older only.
The following code will raise a famous W1057 compiler warning in Delphi 2009:
var s: ShortString;
t: string;
begin
t := s;
end;
To eliminate the warning, just cast the ShortString variable as String and it is compatible with both Delphi 2007 and 2009:
var s: ShortString;
t: string;
begin
t := string(s);
end;
The following code will raise a famous W1057 compiler warning in Delphi 2009:
var s: AnsiString;
t: string;
begin
t := s;
end;
To eliminate the warning, just cast the AnsiString variable as String and it is compatible with both Delphi 2007 and 2009:
var s: AnsiString;
t: string;
begin
t := string(s);
end;
We must take extra care for this warning. Although using the famous cast method may solve the problem, we should only use it only if we understand what we are doing.
For example:
var s: AnsiString;
t: string;
begin
s := t;
end;
If we are very sure that t will contain only ansi string value, then we can perform the cast as follow safely:
var s: AnsiString;
t: string;
begin
s := AnsiString(t);
end;
This warning is usually happens in code invoke legacy external library (*.DLL) that supports PAnsiChar data type only.
We may use curl to upload files to a FTP server in background without user intervention. curl supports resume and retry features as well.
Upload a file to ftp server (-T / --upload-file <file>)
curl -T <file> ftp://server/path/
Upload a file to ftp server that require authentication (-u /-user <user:password>)
curl -u <user>:<password> -T <file> ftp://server/path/
Upload with Retry (--retry <num>) for non stable network connection
curl --retry 50 -u <user>:<password> -T <file> "ftp://server/path/"
Upload with Resuming
curl -C - -u <user>:<password> -T <file> "ftp://server/path/"
Delphi 2009 DBX4 has some behavioral changes compare to Delphi 2007 DBX4. I blog all my study and research against DBX4 here so that I may continue working next time when there are new DBX updates in later official updates from CodeGear.
My first experience on Delphi 2009 DBX4 is not good and full of glitches while I working on it. After spending few days study the DBX4 source (documentation doesn't help much here). I finally come out with my own solution for Delphi 2009 DBX4 in order to make my Delphi 2007 application able to migrate over.
Note: This problem has resolved in Delphi build 12.0.3250.18309.
Deploy DBX4 application on a new machine will always fail at runtime if dbxdrivers.ini and dbxconnections.ini do not exist in folder "%public%\Documents\RAD Studio\dbExpress".
I have post this issue to CodeGear discussion forum and receive pretty good response here: https://forums.codegear.com/message.jspa?messageID=20783#20783
Bob Swart who help me confirm the problem has file a QC report: http://qc.codegear.com/wc/qcmain.aspx?d=67210
The cause of this problem to related to the design of static method TDBXConnectionFactory.GetConnectionFactory in unit DBXCommon.pas. This method is design using singleton pattern that return a TDBXConnectionFactory instance. However, the default instance returned is instantiated from class TDBXIniFileConnectionFactory. This class always return loaded drivers and connections from the 2 *.ini files.
TDBXMemoryConnectionFactory is only used by TSQLConnection.DoConnect in a try...except...end block. I think it's purpose is to create TDBXIniFileConnectionFactory factory first, and if fail due to missing two *.ini files or whatever reason, it will use a TDBXMemoryConnectionFactory instance. However, there are many other DBX operations invoke TDBXMemoryConnectionFactory.GetConnectionFactory too (e.g.: TSQLConnection.SetDriverName). This is not a good design to cover all the holes by try...except...end as in TSQLConnection.DoConnect.
To provide a workaround solution for this problem, I create a TDBXMemoryConnectionFactory instance explicitly and inject it into TDBXConnectionFactory before TDBXConnectionFactory.GetConnectionFactory was invoked. Since it behave as singleton, it won't instantiate the default TDBXIniFileConnectionFactory class any more for it's life time process:
var C: TDBXConnectionFactory;
begin
C := TDBXMemoryConnectionFactory.Create;
C.Open;
TDBXConnectionFactory.SetConnectionFactory(C);
end;
In my DBX application, I create a TSQLConnection instance on the fly as my application may work with many type of database server (e.g.: Firebird, MSSQL or MySQL). I couldn't decide the DriverName at design time. It is up to the end user to state which database server to connect.
As GetDriverFunc, LibraryName and VendorLib property in TSQLConnection seems to provide enough parameters for a database connection, I tend to left TSQLConnection.DriverName empty as it serve no purpose for the connection except filling the 3 properties value mention retrieve from TDBXConnectionFactory.FDrivers collection.
However, an empty DriverName will fail in procedure TSQLConnection.CheckLoginParams invoked by TSQLConnection.DoConnect:
procedure TSQLConnection.CheckLoginParams;
var
I: Integer;
DriverProps: TDBXProperties;
begin
...
if FDriverName = '' then DataBaseError(SMissingDriverName);
...
end;
I personally feel this is an unnecessary checking if I don't rely on two *.ini files to initiate a connection. In order to avoid spending time doing source code patch for this issue, I rather specify a non-empty DriverName value for TSQLConnection:
begin
...
sqlconnection1.DriverName := 'Firebird';
...
end;
Another issue float on now. As I use a workaround solution mentioned in Case 1 to avoid deploying 2 *.ini files, I have no driver instance store in TDBXConnectionFactory.FDrivers collection. When I try to set a value for DriverName, a "TDBXErrorCodes.DriverInitFailed" exception will occurs in SQLConnection.SetDriverName method.
I should register a Firebird dynalink driver to DBX4 framework in order to make DriverName setting work. The code is copy from DBXInterbase.pas and some changes has made allow it work as expected:
unit DBXFirebird;
...
const
sDriverName = 'Firebird';
...
initialization
TDBXDriverRegistry.RegisterDriverClass(sDriverName, TDBXFirebirdDriver);
finalization
TDBXDriverRegistry.UnregisterDriverClass(sDriverName);
end.
You should able to to connect to firebird database with DBX4 now.
No matter what value you set for GetDriverFunc, LibraryName and VendorLib, TSQLConnection will not respect these values. It will only follow the initial values specify in dynalink driver (DBXInterbase.pas).
After tracing the dynalink driver source, I found out the problem occurs in the following method:
constructor TDBXInterBaseDriver.Create(DBXDriverDef: TDBXDriverDef);
begin
inherited Create(DBXDriverDef, TDBXDynalinkDriverLoader);
rpr;
InitDriverProperties(TDBXInterBaseProperties.Create(DBXDriverDef.FDBXContext));
end;
Invoke InitDriverProperties will set a default properties instance into TDBXInterbaseDriver. When the following method is invoke:
procedure TDBXDynalinkDriver.LoadDriver(DBXContext: TDBXContext);
var
Loader: TDBXDynalinkDriverCommonLoader;
begin
if not Assigned(FMethodTable) then
begin
...
Loader.LoadDriverLibraryAndMethodTable(DBXContext, GetDriverProperties);
...
end;
end;
The Loader.LoadDriverLibraryAndMethodTable will always get the default TDBXProperties instance from InitDriverProperties.
I have reported this problem to QC: http://qc.codegear.com/wc/qcmain.aspx?d=67139
After study the source, I found out the problem happens in the following method:
function TDBXDynalinkDriverNative.CreateConnection(ConnectionBuilder: TDBXConnectionBuilder): TDBXConnection;
var
ConnectionHandle: TDBXConnectionHandle;
ErrorResult: TDBXErrorCode;
begin
LoadDriver(ConnectionBuilder.DbxContext);
ErrorResult := FMethodTable.FDBXDriver_CreateConnection(FDriverHandle, ConnectionHandle);
CheckResult(ErrorResult);
Result := TDBXDynalinkConnection.Create(ConnectionBuilder, ConnectionHandle, FMethodTable);
end;
The ConnectionBuilder.ConnectionProperties contain the all the custom setting from TSQLConnection. Unfortunately, it never be used in CreateConnection. Instead, it use the initial properties stored in TDBXDriver.FDriverProperties.
My solution is override the CreateConnection method to make it consume the custom value in ConnectionBuilder.ConnectionProperties:
function TDBXFirebirdDriver.CreateConnection(ConnectionBuilder:
TDBXConnectionBuilder): TDBXConnection;
var
ConnectionHandle: TDBXConnectionHandle;
ErrorResult: TDBXErrorCode;
begin
LoadDriverWithConnectionBuilder(ConnectionBuilder);
ErrorResult := FMethodTable.FDBXDriver_CreateConnection(FDriverHandle, ConnectionHandle);
CheckResult(ErrorResult);
Result := TDBXDynalinkConnection.Create(ConnectionBuilder, ConnectionHandle, FMethodTable);
end;
procedure TDBXFirebirdDriver.LoadDriverWithConnectionBuilder(ConnectionBuilder:
TDBXConnectionBuilder);
var
Loader: TDBXDynalinkDriverLoader_Enhance;
begin
if not Assigned(FMethodTable) then
begin
Loader := FDriverLoaderClass.Create as TDBXDynalinkDriverLoader_Enhance;
try
Loader.LoadDriverLibraryAndMethodTable(ConnectionBuilder.DbxContext, ConnectionBuilder.ConnectionProperties);
FMethodTable := Loader.FMethodTable;
Loader.FMethodTable := nil;
FDriverHandle := Loader.FDriverHandle;
Loader.FreeOldLibrary;
finally
FreeAndNil(Loader.FMethodTable);
Loader.Free;
end;
end;
end;
The loader class TDBXDynalinkDriverLoader_Enhance is duplicated and inherited from TDBXDynalinkDriverLoader as I can't access 2 private methods: FreeOldLibrary and LoadDriverLibraryAndMethodTable:
TDBXDynalinkDriverLoader_Enhance = class(TDBXDynalinkDriverLoader)
private
procedure FreeOldLibrary;
procedure LoadDriverLibraryAndMethodTable(DBXContext: TDBXContext; Properties:
TDBXProperties);
end;
AutoUnloadDriver is a new connection parameter property for Delphi 2009. As stated in DBXCommon.pas for AutoUnloadDriver:
If set to true, dynalink drivers will automatically unload their dll, when there are no longer any open connections that use the driver.
I love this feature as it will release the related DLL if no connection is active.
However, none of the Delphi DBX driver provide this as default setting and there is no way to make AutoUnloadDriver activate.
I have report this problem: QC#67233.
The Dynalink Driver class has the following constructor:
constructor TDBXDynalinkDriver.Create(DBXDriverDef: TDBXDriverDef; DBXDriverLoader: TDBXDynalinkDriverCommonLoaderClass);
begin
inherited Create(DBXDriverDef);
FDriverLoaderClass := DBXDriverLoader;
// '' makes this the default command factory.
//
AddCommandFactory('', CreateDynalinkCommand);
if (DriverProperties = nil) or not DriverProperties.GetBoolean(TDBXPropertyNames.AutoUnloadDriver) then
CacheUntilFinalization;
end;
To make AutoUnloadDriver work as it should, the clue is to avoid invoke CacheUntilFinalization in the constructor. In order to do that, we must make sure DriverProperties is not nil and AutoUnloadDriver property has value "True":
constructor TDBXFirebirdDriver.Create(DBXDriverDef: TDBXDriverDef);
var P: TDBXProperties;
begin
P := TDBXProperties.Create(DBXDriverDef.FDBXContext);
P.Values[TDBXpropertyNames.AutoUnloadDriver] := 'True';
InitDriverProperties(P);
inherited Create(DBXDriverDef, TDBXDynalinkDriverLoader_Enhance);
end;
If you run Delphi IDE on administrator account account, you probably won't encounter any problem launching ModelMaker Code Explorer (MMX).
We mostly work on non-privilege (limited user) account for our daily task since Windows Vista. Installing MMX on administrator account and run Delphi IDE on limited user account will not load the MMX expert.
We have to manually install the MMX for limited user account:
You may follow the steps to migrate old MMX setting to new version:
GPG exist in both Windows and Linux system. It is a tool to perform public key encryption for files or messages. GPG may download from http://www.gnupg.org/
Some useful commands
Delphi project file consist of only one file (.dpk) before Delphi 2006. Beginning of Delphi 2006, MSBUILD (similar to ANT) is used as project build tool. Since then, Delphi 2006 project file consist of 2 files: .DPROJ and .DPK. The out of sync issue between .DPK and .DPROJ cause a lot of problems when working in version control environment.
The .DPROJ is not perfect due to the XML wasn't tidy up nicely. There are some problems with .dproj design:
A .DPROJ that has problems may cause:
You may always follow the steps to re-tidy a .DPROJ that you think it has problems:
# To list all installed packages rpm -qa # To query a package information and dependencies packages rpm -qilR# To query which package require a package rpm -q --whatrequires # To query which package provide the file rpm -q --whatprovides # Test package installation rpm -ivv --test
sysctl -w net.ipv4.ip_forward=1Step 2: Enable IP packet masquerading Firewall (IPTABLES)
# Clearing any existing rules and setting default policy.. iptables -P INPUT ACCEPT iptables -F INPUT iptables -P OUTPUT ACCEPT iptables -F OUTPUT iptables -P FORWARD DROP iptables -F FORWARD iptables -t nat -F # FWD: Allow all connections OUT and only existing and related ones IN iptables -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT # Enabling SNAT (MASQUERADE) functionality on $EXTIF iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADEThe masquerading router should have up once the above script is executed. You may try to ping both eth0 and eth1 to confirm that. Also try to ping public network to make sure it works. You may persist the iptables rules using
service iptables save
var hDesktop: HWND; DC: HDC; T: BLENDFUNCTION; begin hDesktop := GetDesktopWindow; DC := GetDC(hDesktop); try T.BlendOp := AC_SRC_OVER; T.BlendFlags := 0; T.SourceConstantAlpha := $80; T.AlphaFormat := 0; Image1.Canvas.Brush.Color := clGreen; Image1.Canvas.FillRect(Rect(0, 0, Image1.Width, Image1.Height)); Windows.AlphaBlend(Image1.Canvas.Handle, 0, 0, Image1.Width, Image1.Height, DC, 0, 0, Image1.Width, Image1.Height, T); finally ReleaseDC(hDesktop, DC); end; end;
package MyPackage;
{$R *.res}
{$ALIGN 8}
{$ASSERTIONS ON}
{$BOOLEVAL OFF}
{$DEBUGINFO ON}
{$EXTENDEDSYNTAX ON}
{$IMPORTEDDATA ON}
{$IOCHECKS ON}
{$LOCALSYMBOLS ON}
{$LONGSTRINGS ON}
{$OPENSTRINGS ON}
{$OPTIMIZATION OFF}
{$OVERFLOWCHECKS OFF}
{$RANGECHECKS OFF}
{$REFERENCEINFO ON}
{$SAFEDIVIDE OFF}
{$STACKFRAMES OFF}
{$TYPEDADDRESS OFF}
{$VARSTRINGCHECKS ON}
{$WRITEABLECONST OFF}
{$MINENUMSIZE 1}
{$IMAGEBASE $400000}
{$DESCRIPTION 'E Stream Software - Runtime Library'}
{$LIBPREFIX 'SQL.'}
{$RUNONLY}
{$IMPLICITBUILD OFF}
{$DEFINE DEBUG}
The DPK files already has built in compiler directives. It has priority over the switches you specified in command lines. As stated by Allen Bauer in the post:
The IDE supports a very little know feature where you can continue to control these options while in the IDE, yet allow the command-line be able to also control the options. In a package file, all the options listed there are propagated to all the contained units. This is different than a normal .dpr program/library file. In order to do this, all you need to do is replace the '$' with a ' ' (that's aThe solution is replace $ with a space character (' ') for all compiler directives only:). Then when you open the dpk in the IDE, you can toggle those options as much as you like, but when you compile on the command-line, you can still control them. This is how we build all our packages for the product itself. All of the Borland built packages have DEBUGINFO, STACKFRAMES, ASSERTIONS, OPTIMIZATION, LOCALSYMBOLS setup this way because like you, we wan't to be able to control those options from the command-line. The developers will typically do a complete "debug" build, whereas the integration team will not. $DEFINES will sort of work the same way, in that if you replace the '$' with a ' ', the IDE will still recognize the defines and apply them, but any other modifications to the dpk source will re-insert the '$' character.
package MyPackage;
{$R *.res}
{$ALIGN 8}
{ ASSERTIONS ON}
{ BOOLEVAL OFF}
{ DEBUGINFO ON}
{ EXTENDEDSYNTAX ON}
{ IMPORTEDDATA ON}
{ IOCHECKS ON}
{ LOCALSYMBOLS ON}
{ LONGSTRINGS ON}
{ OPENSTRINGS ON}
{ OPTIMIZATION OFF}
{ OVERFLOWCHECKS OFF}
{ RANGECHECKS OFF}
{ REFERENCEINFO ON}
{ SAFEDIVIDE OFF}
{ STACKFRAMES OFF}
{ TYPEDADDRESS OFF}
{ VARSTRINGCHECKS ON}
{ WRITEABLECONST OFF}
{ MINENUMSIZE 1}
{$IMAGEBASE $400000}
{$DESCRIPTION 'E Stream Software - Runtime Library'}
{$LIBPREFIX 'SQL.'}
{$RUNONLY}
{$IMPLICITBUILD OFF}
{$DEFINE DEBUG}
By doing so, both the IDE and DCC32 will respect the switches and yield expected results and.
The output files (DLL, BPL or EXE) do not contain any debugging information even if you turn on the debugging switches. Those debugging information are stored in DCU or DCP files.
To keep the debug information in DLL, BPL or EXE, turn on the Include TD32 debug info or use -V switch with DCC32.
uses SHFolder;
var sDir: string;
begin
SetLength(sDir, MAX_PATH);
ZeroMemory(@sDir[1], MAX_PATH);
if Succeeded(SHGetFolderPath(0, CSIDL_PERSONAL, 0, 0, PAnsiChar(sDir))) then
ShowMessage(sDir);
end;
NewXMLText := StringReplace(XMLText, #13#10, ' ', [rfReplaceAll, rfIgnoreCase]);
var S: TStringList;
M: TStream;
begin
S := TStringList.Create;
M := TMemoryStream.Create;
try
S.Values['Email'] := 'your google account';
S.Values['Passwd'] := 'your password';
S.Values['source'] := 'estream-sqloffice-1.1.1.1';
S.Values['service'] := 'cl';
IdHTTP1.IOHandler := IdSSLIOHandlerSocketOpenSSL1;
IdHTTP1.Request.ContentType := 'application/x-www-form-urlencoded';
IdHTTP1.Post('https://www.google.com/accounts/ClientLogin', S, M);
Memo1.Lines.Add(Format('Response Code: %d', [IdHTTP1.ResponseCode]));
Memo1.Lines.Add(Format('Response Text: %s', [IdHTTP1.ResponseText]));
M.Position := 0;
S.LoadFromStream(M);
Memo1.Lines.AddStrings(S);
finally
S.Free;
M.Free;
end;
end;