Forum > Windows (32/64)
Build Lazarus from main branch source code failed in windows
hawkx:
In the past two days, I built Lazarus through source code from main branch in Windows 10. There was an error occurred,the message is:
--- Quote ---(10001) PPU Loading C:\Develop\Lazarus\components\virtualtreeview\lib\i386-win32-win32\laz.vtideeditors.ppu
(10011) PPU Source: laz.vtideeditors.pas not found
(10028) Recompiling laz.VTIDEEditors, checksum changed for C:\Develop\Lazarus\components\virtualtreeview\lib\i386-win32-win32\laz.virtualtrees.ppu
Fatal: (10022) Can't find unit laz.VTIDEEditors used by laz.RegisterVirtualTreeView
Fatal: (1018) Compilation aborted
--- End quote ---
Finally, I found that this issue can be corrected through the following modifications:
* 1. Modify laz.virtualtreeview_package.pas, change the order of laz.VTIDEEditors in the uses statement. change
--- Code: Pascal [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---uses laz.VirtualTrees, laz.VTHeaderPopup, laz.RegisterVirtualTreeView, laz.VTGraphics, laz.VTIDEEditors, LazarusPackageIntf;to
--- Code: Pascal [+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i < x.length; i++) { x[i].style.maxHeight='none'; x[i].style.height = Math.min(x[i].clientHeight+15,306)+'px'; x[i].style.resize = "vertical";}};} ---uses laz.VirtualTrees, laz.VTHeaderPopup, laz.VTIDEEditors, laz.RegisterVirtualTreeView, laz.VTGraphics, LazarusPackageIntf;I know this file was automatically created by Lazarus, but I had to do this to make the command "make clean all" runs correctly.
* 2. Modify laz.virtualtreeview_package.lpk, change the order of laz.vtideeditors.pas, change
--- Quote --- <Item>
<Filename Value="laz.registervirtualtreeview.pas"/>
<HasRegisterProc Value="True"/>
<UnitName Value="laz.RegisterVirtualTreeView"/>
</Item>
<Item>
<Filename Value="laz.vtgraphics.pas"/>
<UnitName Value="laz.VTGraphics"/>
</Item>
<Item>
<Filename Value="laz.virtualtrees.res"/>
<Type Value="Binary"/>
</Item>
<Item>
<Filename Value="laz.vtideeditors.pas"/>
<UnitName Value="laz.VTIDEEditors"/>
</Item>
--- End quote ---
to
--- Quote --- <Item>
<Filename Value="laz.vtideeditors.pas"/>
<UnitName Value="laz.VTIDEEditors"/>
</Item>
<Item>
<Filename Value="laz.registervirtualtreeview.pas"/>
<HasRegisterProc Value="True"/>
<UnitName Value="laz.RegisterVirtualTreeView"/>
</Item>
<Item>
<Filename Value="laz.vtgraphics.pas"/>
<UnitName Value="laz.VTGraphics"/>
</Item>
<Item>
<Filename Value="laz.virtualtrees.res"/>
<Type Value="Binary"/>
</Item>
--- End quote ---
This is the real place to change the order of the laz.VTIDEEditors, to prevent Lazarus building fail during install/uninstall packages.
Somebody please verify this issue, and sumbit to Lazarus Gitlab if above modification works properly. Thanks!
marcov:
Do you also use FPC trunk? Some work is being done there on the unit order.
hawkx:
--- Quote from: marcov on March 14, 2024, 03:16:32 pm ---Do you also use FPC trunk? Some work is being done there on the unit order.
--- End quote ---
I used main branch of FPC too.
dsiders:
--- Quote from: hawkx on March 14, 2024, 03:18:34 pm ---
--- Quote from: marcov on March 14, 2024, 03:16:32 pm ---Do you also use FPC trunk? Some work is being done there on the unit order.
--- End quote ---
I used main branch of FPC too.
--- End quote ---
I just built Lazarus 3.99-1660-g7400dc43b0 using both FPC 3.2.2 and FPC 3.3.1-15189-gae06528db4 (2024-02-18). No issues.
So your problem is not with Lazarus source code.
hawkx:
--- Quote from: dsiders on March 14, 2024, 03:32:14 pm ---
I just built Lazarus 3.99-1660-g7400dc43b0 using both FPC 3.2.2 and FPC 3.3.1-15189-gae06528db4 (2024-02-18). No issues.
So your problem is not with Lazarus source code.
--- End quote ---
This issue only occurred while build for win32-i386, not occurs while "make clean all OS_TARGET=win64 CPU_TARGET=x86_64", are you built for win32-i386
Navigation
[0] Message Index
[#] Next page