Removing Debug & Packages from settings
lazarus / 31-LCL

----------------------------------------------------------------------
newbie2lazarus · 2012-06-27 05:36

Newbie to Lazarus, how do i remove all the debug info, lazarus forms &
resources(like icons, etc) from ide settings, just as if i were
compiling with ppc386. i mean all those infos make the output so big.

----------------------------------------------------------------------
exdatis · 2012-06-27 05:41

You may shrink exe file with:
 strip --strip-all your_app (command line).
Regards.
see: http://wiki.freepascal.org/Lazarus_Faq#Why_are_the_generated_bina
ries_so_big.3F

----------------------------------------------------------------------
newbie2lazarus · 2012-06-27 05:49

THank you that did it but how do i set the settings in lazarus so that
i dont have icons in build so that i dont have to remove them manually
everytime ?

----------------------------------------------------------------------
exdatis · 2012-06-27 06:00

I'm not sure, see:
http://wiki.freepascal.org/Lazarus_Resources
Regards.

----------------------------------------------------------------------
CaptBill · 2012-06-27 06:08

Go to main menu|project|project options then in that dialog go to
compiler options "linking" treeview tab.
Then uncheck "generate debugging info..." . Pick "strip" also if you
want that. Also you can choose "smart linking" here as well. At the
bottom left of the window is the "use these settings as default"
checkbox if you desire it.

----------------------------------------------------------------------
BigChimp · 2012-06-27 06:44

Yep, what CaptBill said. In newer Lazarus version you can create a new
"build mode", call it e.g. Debug (the existing one is default). In
debug mode, youc an enable debug symbol output, disable linking, set
optimizations to 0 etc.

Now you can quickly switch between debug and release builds (there's a
button/drop down on the toolbar that lets you do that).

I wouldn't mess with strip though....  it's been taken out of newer
FPC distributions because often its disadvantages outweigh its
benefits.
See the "why are the executables so big" wiki page for more details on
debug info, strip, etc.

----------------------------------------------------------------------
CaptBill · 2012-06-27 07:30

Hey BigChimp

Also, and this was something that tripped me up early on: don't get
the Tools|Options and the Project|Project Options confused. Get really
acquainted here. These are probably the two places you will be going
most often.

I forgot to answer the question about loading libs and .res etc. etc.
That is at project level, Project|Project Inspector. All your extras
are here in an editable treeview.

Make that three places you will see and need most often in the design
time environment.

Also, I wish I knew about the  "Code Explorer" sooner than I did. It
makes a good 'OOP code spellchecker'. If you have a syntax error it
reflects in the treeview of the Code Explorer. Just refresh every once
in a while, and if the treeview is "correct", your code tree views as
expected. If not, you know you need to chase down the error. Really
cool feature.

Also be sure you understand the powers of the code-completion
abilities. Really, really top notch. That and the code-explorer tree-
check abilities and the interface is seriously sweet.