Mailing lists / lazarus / 2011-02
4 messages · 3 people ·
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Hi all,
Now the LCL is automatically recompiled when some change has been detected, what do I do if I change something in the FCL/RTL and want to rebuild the LCL? And all packages in one go? (Checking which package depend on the rtl/fcl change and compile them manually is too much work, I discovered after a few days of brain-dead compilations)
Joost.
That's a very common problem in software development and the answer is always: make clean
In this particular case, open the LCL package and one of the options is "Recompile clean"
And for your project "Build all" should do it
No idea if when you depend on a lot of packages if you will need to rebuild each of them clean separately.
Yes, offcourse. But before this change I had a window in which I could do this easily. Recompile the LCL/IDE and packages in one go.
And for your project "Build all" should do it No idea if when you depend on a lot of packages if you will need to rebuild each of them clean separately.
Maybe I can try that. I recompiled all packages manually, but maybe that after a forced LCL compile, all packages are compiled when I do 'build all' on the project.
Joost.
Now the LCL is automatically recompiled when some change has been detected, what do I do…
The IDE only checks the dates of the fpc.cfg and the compiler executable. This means installation of a new compiler is recognized, but changes only to the ppu files are not recognized.
Checking that every time would take some time, especially under windows. Since only experts do the above and experts don't want slow down, I think it makes no sense to implement that.
If you compile the FCL/RTL via a script you could remove the file lazarus/packager/units/cpu-os/FCL.compiled.
Because normally every package uses that one, the IDE will recompile all packages.
Mattias