Frank Church wrote 29 lines
On 22 March 2011 18:15, Mattias Gaertner wrote:
> On Wed, 23 Mar 2011 00:44:43 +1100
> Peter Williams wrote:
>
> >[...]
> > >Recompiling IdStreamVCL, checksum changed for IdGlobal
> > >IdStreamVCL.pas(13,20) Fatal: Can't find unit IdStreamVCL used by
> IdStream
>
> You can try compiling the Indy package with -Ur. Add this to the
> compiler options of the Indy package.
>
>
> > >What do they actually mean, in particular which process is emitting the
> message Fatal: Can't find unit IdStreamVCL used by IdStream?
>
> Process: fpc
> Meaning: a ppu file is outdated. There is a bug in fpc that can trigger
> this. There are several ways to work around the bug. One is to use -Ur.
>
>
>
I will test your suggestion. I have always suspected that there some bugs
in FPC that Indy triggers.
After trying it out it now compiling is okay, but when it comes to registration it stops on the file indylaz.pas, which is the file that registers the components.
It is sensible or the norm for the unit that does the registration to have the same base name of the project file?
ie indylaz.pas and indylaz.lpk
The file also appears to be created at compile time
Show quoted text 29 lines
{ This file was automatically created by Lazarus. do not edit!
This source is only used to compile and install the package.
}
unit indylaz;
interface
uses
IdAbout, IdAboutVCL, IdAntiFreeze, IdCoreDsnRegister, IdDsnBaseCmpEdt,
IdDsnCoreResourceStrings, IdDsnPropEdBinding, IdDsnPropEdBindingVCL,
IdDsnRegister, IdDsnResourceStrings, IdDsnSASLListEditor,
IdDsnSASLListEditorForm, IdDsnSASLListEditorFormVCL, IdRegister,
IdRegisterCore, LazarusPackageIntf;
implementation
procedure Register;
begin
RegisterUnit('IdCoreDsnRegister', @IdCoreDsnRegister.Register);
RegisterUnit('IdDsnRegister', @IdDsnRegister.Register);
RegisterUnit('IdRegister', @IdRegister.Register);
RegisterUnit('IdRegisterCore', @IdRegisterCore.Register);
end;
initialization
RegisterPackage('indylaz', @Register);
end.
Show quoted text 17 lines
