In the fpc-pascal ML, Martin said:

If you work on the IDE itself try the package IdeInspector (it adds itself to "view" > "Ide Internals" if installed)

Is there a "best practice" way of installing Lazarus packages at build time, to avoid the extra time of a second build once the IDE is running (possibly followed by another build of librarees etc. once the first project is compiled)?

When I started using a local svn repository I patched lazsvnpkg into the makefiles etc. which appears to work OK with fairly recent versions of Lazarus (from around 0.9.26), but I'm not entirely happy with it since strictly the patch should be regenerated each time in case the sources have changed.

Mark Morgan Lloyd hat am 2. M?rz 2012 um
12:18 geschrieben:

Why do you build two times?
Why not simply svn up und rebuild the IDE via the IDE?

colleagues]

Mattias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120302/9ba8edd6/attachment.html>

2012/3/2 Mattias Gaertner :

Why do you build two times? Why not simply svn up und rebuild the IDE via the IDE?

I think I know what the problem is, I also wondered what would be the best solution for this and found nothing. The problem is the "build lazarus" from within Lazarus is using a somehow different way to buil it. From the console output it looks like "build lazarus" is *somehow* making use of the same makefiles too but it is producing a different result when running the same make target from the console.

I think with "build two times" when doing a fresh install (or after fixing a broken unrunnable lazarus) he refers to:

svn checkout .... (or svn up -r <known_working> or otherwise fix broken things)
make clean all <--- this is the first time

and then from the menu
./lazarus
Tools -> build lazarus <-- this is the second time.

There should be a make target that does exactly the same as the menu item "build lazarus", somehow the highly obscure make-voodoo that is performed in the "build lazarus" menu command should also be accessible from the console without having any working Lazarus binary. I once tried to reverse-engineer what exactly is going on and how and why calling the *same* make target would produce different outcomes when called from within the IDE and the command line but eventually I gave up.

If you want to build the IDE with packages use
lazbuild --build-ide=

Mattias

Sorry, I missed the earlier messages.

I've just compiled 0.9.30.4rc, and I no longer see a problem. However until comparatively recently if you got Lazarus using svn co (etc.) and then did a make bigide with default settings, the first project you built also recompiled a whole lot of underlying libraries.

Many thanks to whoever fixed this. However once aware of the issue I didn't consider it to be a particularly big deal, more serious is any requirement to rebuild the IDE "from inside" since on tight systems this obviously depletes the resources available for the compiler and- in particular- linker.

What do you mean- like

lazbuild --build-ide=lazsvnpkg

as an alternative to make all ? In that case what's the basic package list corresponding to bigide?

It recompiles if you added custom options in the Configure build Lazarus dialog.
If you have the default settings the 0.9.31 IDE should only recompile the IDE and the packages that are not in bigide, aka your additional installed packages. If you found a different behavior please report the bug.

No.
There is currently no command line tool to change the list of install packages. lazbuild takes the list from the same place as the IDE - your config directory.
The parameter --build-ide takes additional compiler options. Like debugger settings, verbosity, checks or defines. To compile an IDE with your current list of installed packages use

lazbuild --build-ide=

Mattias

Until recently an IDE built with make bigide recompiled at least some packages when told to build the first project. This was irrespective of whether I was patching in e.g. lazsvnpkg.

If you have the default settings the 0.9.31 IDE should only recompile the IDE and the packages that are not in bigide, aka your additional installed packages. If you found a different behavior please report the bug.

It's apparently been fixed, but I'll keep an eye on it.

OK. So going back to my original query: if I want to add something like lazsvnpkg for the initial build I've got to patch it in myself.

i want to make sure i am understanding this completely... i've been using the wiki's install FPC and Lazarus from SVN methods for a while... i even contributed a little bit to that page... anyway, i currently have the following script...

=============== snip ===============
@echo off
echo %0 executing...

:setvars
if "%myFPCver%" == "" set myFPCver=2.4.5
if "%myFPCpath%" == "" set myFPCpath=c:\freepascal\fpc\%myFPCver% if "%myLAZpath%" == "" set myLAZpath=c:\freepascal\laz if "%myFPCbinutils%" == "" set myFPCbinutils=c:\freepascal\binutils if "%myFPCpathset%" == "TRUE" goto pathok
set PATH=%myFPCbinutils%\i386-win32;%myFPCpath%\bin\i386-win32;%PATH% set myFPCpathset=TRUE
:pathok

echo before update, make clean...
cd %myLAZpath%
make clean
echo make clean complete...

echo updating lazarus from svn...
TortoiseProc /command:update /path:"%myLAZpath%"
echo svn update complete...

echo compiling lazarus...
rem cd %myLAZpath%
rem make clean all OPT="-glw2"
echo lazarus compilation complete...

:end
echo %0 execution complete!
pause
=============== snip ===============

if i am understanding correctly, i can take the "echo compiling lazarus" section and fix it up like this??

echo compiling lazarus...
cd %myLAZpath%
lazbuild --build-ide=
echo lazarus compilation complete...

and it will be the same thing as if i started lazarus and used the tools->build lazarus option?

if one has several build lazarus options in place, can lazbuild be told to use a certain one? eg: i have normal, debug and optimized build options...

getting the command building of lazarus working has been on my todo list since a long time... if this is the way, then i will finally be able to open a command prompt, type updatelaz, hit enter and go get my coffee while it churns out one (or three different) new lazarus exe(s) for me :)

make clean lazbuild OPT="-glw2"

No.
But you can pass the options in --build-ide="your options".

getting the command building of lazarus working has been on my todo list since a long time... if this is the way, then i will finally be able to open a command prompt, type updatelaz, hit enter and go get my coffee while it churns out one (or three different) new lazarus exe(s) for me :)

Mattias

ok... still trying to fully understand... sorry :(

are you saying that i should have the following? (the OPTS are taken from the options in the attached Debug IDE screen shot)

echo compiling lazarus...
cd %myLAZpath%
make clean lazbuild OPT="-gw -gl -godwarfsets -gh -gt -Co -Cr -Ci -Sa" echo lazarus compilation complete...

those are for my "Debug IDE" but i don't want all those options for the optimized and normal IDEs... in fact, those OPT options do not exist in the normal profile and they are different in the optimized profile...

alright... having read over this numerous times, like this then???

echo compiling lazarus...
cd %myLAZpath%
echo Debug IDE
make clean lazbuild --build-ide="-gw -gl -godwarfsets -gh -gt -Co -Cr -Ci -Sa" copy lazarus.exe lazarus-debug.exe
echo Normal IDE
make clean lazbuild --build-ide=
copy lazarus.exe lazarus-normal.exe
echo Optimized IDE
make clean lazbuild --build-ide="-O2 -g- -Xs"
copy lazarus.exe lazarus-optimized.exe
echo lazarus compilation complete...

so what about the "DEBUG" and "VERBOSE" check boxes? and the all important "update revision.inc"?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config laz - debug ide.png
Type: image/png
Size: 10318 bytes
Desc: not available
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120308/b303224e/attachment-0003.png> -------------- next part --------------
A non-text attachment was scrubbed...
Name: config laz - normal ide.png
Type: image/png
Size: 9888 bytes
Desc: not available
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120308/b303224e/attachment-0004.png> -------------- next part --------------
A non-text attachment was scrubbed...
Name: config laz - optimized ide.png
Type: image/png
Size: 10035 bytes
Desc: not available
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20120308/b303224e/attachment-0005.png>

echo compiling lazarus...
cd %myLAZpath%
make clean lazbuild
lazbuild.exe --build-ide="-gw -gl -godwarfsets -gh -gt -Co -Cr -Ci -Sa" echo lazarus compilation complete...

Keep in mind that if the options are different in the IDE settings the IDE will rebuild the packages again.

Maybe the --build-mode parameter can be extended to set the mode for the IDE building.

[...]

Mattias

that would be a great step forward because right now it is rather confusing even to myself who has been doing this stuff for years...

maybe something like --build-ide-profile which pulls /ALL/ settings from the profile named? this would eliminate the rebuilding stuff since it seems like there is to be a double build even with what you show me to use...

The current build profiles are the build modes of the IDE. Eventually the IDE should be compiled as a project. Then they will be called build modes. That's why it should use the same parameter as a project --build-mode.

Mattias

Mattias Gaertner wrote

The current build profiles are the build modes of the IDE. Eventually the IDE should be compiled as a project. Then they will be called build modes. That's why it should use the same parameter as a project --build-mode.

ok... so if i am understanding this correctly, and i think i am, you are saying that in the future we could write

lazbuild --build-mode="debug ide"

and it would build the same as if invoked from within the IDE with the "Debug IDE"*1 profile selected? if so, that's great and kinda pretty much what i have been looking for and kinda expecting to find in a manner of speaking ;)

now that we have these IDE (or per project?) compile profiles, it just makes sense that we can select them from the command line with the proper tool...

*1 yes, i played a case sensitive card there ;)

Mattias Gaertner wrote

cd %myLAZpath% make clean lazbuild lazbuild.exe --build-ide="-gw -gl -godwarfsets -gh -gt -Co -Cr -Ci -Sa"

ik, so i have fixed up my script to follow the above... there is a make clean beforehand... i see this in the output but compilation seems to carry on and a valid and current IDE exe seems to be generated... what does this mean?

c:/freepascal/binutils/i386-win32/rm.exe -f *.s *_ppas.bat make[1]: Leaving directory `C:/freepascal/laz/ideintf' make -C lcl/interfaces/nogui
make[1]: Entering directory `C:/freepascal/laz/lcl/interfaces/nogui' c:/freepascal/binutils/i386-win32/rm.exe -f ../../units/i386-win32/nogui/interfa ces.ppu \
../../units/i386-win32/nogui/interfaces.o
c:/freepascal/fpc/2.4.5/bin/i386-win32/ppc386.exe -gl -dnogui -Fu../../units/i38 6-win32 -Fu../../../components/lazutils/lib/i386-win32 -Fu. -FE. -FU../../units/ i386-win32/nogui -di386 interfaces.pp
Free Pascal Compiler version 2.4.5 [2011/06/01] for i386 Copyright (c) 1993-2010 by Florian Klaempfl
Target OS: Win32 for i386
Compiling interfaces.pp
Fatal: Can't find unit InterfaceBase used by Interfaces Fatal: Compilation aborted
make[1]: *** [interfaces.ppu] Error 1
make[1]: Leaving directory `C:/freepascal/laz/lcl/interfaces/nogui' make: *** [lazbuilder] Error 2
TBuildManager.SetBuildTargetIDE OS=win32 CPU=i386 WS=win32 TFPCTargetConfigCache.NeedsUpdate compiler file changed "C:\freepascal\fpc\2.4.5 \bin\i386-win32\fpc.exe" FileAge=1052875024 StoredAge=0 TFPCTargetConfigCache.Update C:\freepascal\fpc\2.4.5\bin\i386-win32\fpc.exe Targ etOS=win32 TargetCPU=i386 CompilerOptions= ExtraOptions=-FrC:\freepascal\laz\com ponents\codetools\fpc.errore.msg PATH=c:\freepascal\binutils\i386-win32;c:\freep ascal\fpc\2.4.5\bin\i386-win32;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem ;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\TortoiseSV N\bin;C:\Program Files\GnuWin32\bin;
RunTool C:\freepascal\fpc\2.4.5\bin\i386-win32\fpc.exe -iTOTP -Pi386 -Twin32 -Fr C:\freepascal\laz\components\codetools\fpc.errore.msg