ZeosDBO

[WJSwanepoel]

When trying to install ZeosDBO (7.1.4) on Lazarus 1.6.4 it give me a whole load of messages I have no idea what to do about. Can anybody assist? I am new to Lazarus.

Messages, Hints: 154
Note: Duplicate unit "ZSybaseToken" in "zcore 7.1", orphaned ppu "C:\Zeos\packages\lazarus\lib\x86_64-win64\ZSybaseToken.ppu"
Note: Duplicate unit "ZSybaseToken" in "zparsesql 7.1", ppu="C:\Zeos\packages\lazarus\lib\x86_64-win64\ZSybaseToken.ppu", source="C:\Zeos\src\parsesql\ZSybaseToken.pas"
Note: Duplicate unit "ZSybaseAnalyser" in "zcore 7.1", orphaned ppu "C:\Zeos\packages\lazarus\lib\x86_64-win64\ZSybaseAnalyser.ppu"
Note: Duplicate unit "ZSybaseAnalyser" in "zparsesql 7.1", ppu="C:\Zeos\packages\lazarus\lib\x86_64-win64\ZSybaseAnalyser.ppu", source="C:\Zeos\src\parsesql\ZSybaseAnalyser.pas"
Note: Duplicate unit "ZSqLiteToken" in "zcore 7.1", orphaned ppu "C:\Zeos\packages\lazarus\lib\x86_64-win64\ZSqLiteToken.ppu"
Note: Duplicate unit "ZSqLiteToken" in "zparsesql 7.1", ppu="C:\Zeos\packages\lazarus\lib\x86_64-win64\ZSqLiteToken.ppu", source="C:\Zeos\src\parsesql\ZSqLiteToken.pas"
Note: Duplicate unit "ZSqLiteAnalyser" in "zcore 7.1", orphaned ppu "C:\Zeos\packages\lazarus\lib\x86_64-win64\ZSqLiteAnalyser.ppu"
Note: Duplicate unit "ZSqLiteAnalyser" in "zparsesql 7.1", ppu="C:\Zeos\packages\lazarus\lib\x86_64-win64\ZSqLiteAnalyser.ppu", source="C:\Zeos\src\parsesql\ZSqLiteAnalyser.pas"
Note: Duplicate unit "ZSelectSchema" in "zcore 7.1", orphaned ppu "C:\Zeos\packages\lazarus\lib\x86_64-win64\ZSelectSchema.ppu"
Note: Duplicate unit "ZSelectSchema" in "zparsesql 7.1", ppu="C:\Zeos\packages\lazarus\lib\x86_64-win64\ZSelectSchema.ppu", source="C:\Zeos\src\parsesql\ZSelectSchema.pas"
Note: Duplicate unit "ZScriptParser" in "zcore 7.1", orphaned ppu "C:\Zeos\packages\lazarus\lib\x86_64-win64\ZScriptParser.ppu"
Note: Duplicate unit "ZScriptParser" in "zparsesql 7.1", ppu="C:\Zeos\packages\lazarus\lib\x86_64-win64\ZScriptParser.ppu", source="C:\Zeos\src\parsesql\ZScriptParser.pas"
Note: Duplicate unit "ZPostgreSqlToken" in "zcore 7.1", orphaned ppu "C:\Zeos\packages\lazarus\lib\x86_64-win64\ZPostgreSqlToken.ppu"

Etc... can't post it all.

[carl_caulkett]

I had a similar problem a few months ago. I was told to do "Run" -> "Clean up and Build". It takes a while to rebuild everything but it cleared up my problems. Good luck!

[WJSwanepoel]

Thank you, I will give it a try.

[WJSwanepoel]

I tried it and I get another batch of weird messages:
Compile package FCL 1.0.1: Success
Compile package LazUtils 1.0: Success, Warnings: 9, Hints: 4
winlazutf8.inc(351,6) Note: Local variable "ResultLen" not used
lazfileutils.inc(387,18) Warning: Symbol "faSysFile" is not portable
lazfileutils.inc(389,17) Warning: Symbol "faHidden" is not portable
lazfileutils.inc(390,19) Warning: Symbol "faVolumeId" is deprecated
lazfileutils.inc(390,19) Warning: Symbol "faVolumeId" is not portable
lazfileutils.inc(391,18) Warning: Symbol "faSymLink" is not portable
lazfileutils.pas(109,23) Hint: Parameter "ExceptionOnError" not used
lazfilecache.pas(75,65) Hint: Parameter "EmptyOnError" not used
winfileutil.inc(21,53) Warning: Symbol "UTF8ToSys" is deprecated: "Use the function in LazUTF8 unit"
winfileutil.inc(21,13) Warning: Symbol "SysToUTF8" is deprecated: "Use the function in LazUTF8 unit"
lazutf8sysutils.pas(39,35) Hint: Local variable "SystemTime" does not seem to be initialized
lazfreetypefontcollection.pas(909,45) Warning: Symbol "faVolumeId" is deprecated
lazfreetypefontcollection.pas(909,45) Warning: Symbol "faVolumeId" is not portable
Compile package LCLBase 1.6.4: Success, Warnings: 15
translations.pas(1218,113) Warning: Symbol "Create" is deprecated: "use options form instead"
shellctrls.pas(698,47) Warning: Symbol "faHidden" is not portable
shellctrls.pas(698,58) Warning: Symbol "faHidden" is not portable
shellctrls.pas(803,67) Warning: Symbol "faHidden" is not portable
shellctrls.pas(810,43) Warning: Symbol "faHidden" is not portable
shellctrls.pas(875,70) Warning: Symbol "faSysFile" is not portable
shellctrls.pas(875,81) Warning: Symbol "faHidden" is not portable
shellctrls.pas(1073,36) Warning: Symbol "faHidden" is not portable
shellctrls.pas(1073,48) Warning: Symbol "faHidden" is not portable
shellctrls.pas(1105,52) Warning: Symbol "faHidden" is not portable
filectrl.pp(302,30) Warning: Comment level 2 found
filectrl.pp(314,26) Warning: Symbol "faHidden" is not portable
filectrl.pp(315,27) Warning: Symbol "faSysFile" is not portable
filectrl.pp(316,28) Warning: Symbol "faVolumeId" is deprecated
filectrl.pp(316,28) Warning: Symbol "faVolumeId" is not portable
Compile package LCL 1.6.4: Success, Warnings: 8
win32proc.pp(717,41) Warning: Symbol "Handle" is deprecated: "use Reference.Handle instead"
win32int.pp(21,26) Warning: User defined: Fix implicit pointer conversions
win32pagecontrol.inc(71,17) Warning: Symbol "IsUnpaged" is deprecated
win32pagecontrol.inc(334,24) Warning: Symbol "IsUnpaged" is deprecated
win32pagecontrol.inc(644,18) Warning: Symbol "IsUnpaged" is deprecated
win32callback.inc(561,58) Warning: Local variable "BytesCount" does not seem to be initialized
win32int.pp(296,6) Warning: Symbol "GetTickCount" is deprecated: "Use GetTickCount64 instead"
win32int.pp(297,22) Warning: Symbol "GetTickCount" is deprecated: "Use GetTickCount64 instead"
Compile Project, Target: C:\Users\WILLEM~1\AppData\Local\Temp\project1.exe: Success

[carl_caulkett]

At a glance, I would say that the messages this time a more to do with the application itself, possibly because you are using functions that give rise to warnings about potential cross platform issues.

For example, the lazfileutils.inc(387,18) Warning: Symbol "faSysFile" is not portable message has arisen because you are using Windows only file attributes. Depending on your intended audience, this may not be a problem.

Similarly, where you are getting deprecated this shows that you are using constructs that although they may work at the moment, are intended for withdrawal in later versions of the compiler. 

For example, you are getting the warning Warning: Symbol "Handle" is deprecated: "use Reference.Handle instead". In this case, I would recommend trusting that the compiler knows what it is talking about, and to use Reference.Handle rather than Handle.

I reckon, that with a bit of careful cleaning up of your source code, you should be able to get rid of all of those messages. On the plus side, your application has actually compiled! The compiler is just warning you of potential future problems.

[carl_caulkett]

It's also worth pointing out that if you look in Project Options -> Compiler Options -> Verbosity you can control how strict the reporting of the compiler actually is. it's then a case of striking a balance between having a nice "clean" compilation, which may feel superficially good, against the deeper satisfaction of actually weeding out those problems and getting a genuinely clean build. As you get more experienced, you will undoubtedly lean towards the latter approach.