Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2016-03

Lazarus svn trunk compilation broken under Windows

4 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Sandro Cumerlato
win32wscustomlistview.inc(84,15) Error: Incompatible types: got

"TYPES.TSmallPoint" expected "WINDOWS.TSmallPoint"

win32wscomctrls.pp(1017) Fatal: There were 1 errors compiling module,

stopping

Fatal: Compilation aborted

Please review attached patch and apply if ok.

Sandro Cumerlato
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20160306/5083ba1f/attachment.html> -------------- next part --------------
Index: lcl/interfaces/win32/win32wscustomlistview.inc =================================================================== --- lcl/interfaces/win32/win32wscustomlistview.inc (revision 51831) +++ lcl/interfaces/win32/win32wscustomlistview.inc (working copy) @@ -81,7 +81,7 @@

       P.X:=0;
       P.Y:=0;
     end;

- Result := PointToSmallPoint(P);
+ Result := Windows.PointToSmallPoint(P);

   end;
   procedure HandleListViewOwnerData(ALV: TCustomListViewAccess);

Reply by email

zeljko
to Sandro Cumerlato
Sandro Cumerlato wrote 7 lines
> win32wscustomlistview.inc(84,15) Error: Incompatible types: got "TYPES.TSmallPoint" expected "WINDOWS.TSmallPoint" > win32wscomctrls.pp(1017) Fatal: There were 1 errors compiling module, stopping > Fatal: Compilation aborted Please review attached patch and apply if ok.

Pls open an issue about it (if it's not fixed already) and attach patch.

zeljko

Reply by email

Bart
to zeljko
zeljko wrote 8 lines
> > win32wscustomlistview.inc(84,15) Error: Incompatible types: got > "TYPES.TSmallPoint" expected "WINDOWS.TSmallPoint" > > win32wscomctrls.pp(1017) Fatal: There were 1 errors compiling module, > stopping > > Fatal: Compilation aborted > Pls open an issue about it (if it's not fixed already) and attach patch.

Already fixed in r51838.

Bart

Reply by email