Dear list,

Since lazarus has changed default debug info to dwarf, packages that are automatically compiled are systematically compiled with dwarf debug info. In a wince cross compiling environment this particularly annoying since the 2.4.4 wince cross compiler (actually the cross assembler provided with it) doesn't support the .secrel32 pseudo command issued by the compiler for debug info http://bugs.freepascal.org/view.php?id=20362. Configuring the lazarus build settings to stabs or no debug doesn't help. Project settings aren't changing anything either. How can I change the default compiler settings for packages? Am I missing something or is this a bug? Other than the dwarf problem, how to compile code without debug info in the packages?

To reproduce the problem: in a new lazarus wince cross environment drop a tmemdataset on a form. Set project options to create stabs. Compile. Aborts with
G:\lazarusce\components\memds\lib\arm-wince\wince\frmselectdataset.s:1521: Error: unknown pseudo-op: `.secrel32'

Makefile.compiled for memds package says:
<?xml version="1.0"?>
<CONFIG>
<Makefile Value="True"/>
<Params Value=" -MObjFPC -Scgi -O1 -gw2 -godwarfsets -gl -vewnhi -l -Fu../../ideintf/units/%(CPU_TARGET)-%(OS_TARGET);../../lcl/units/%(CPU_TARG ET)-%(OS_TARGET)/%(LCL_PLATFORM);../../lcl/units/%(CPU_TARGET)-%(OS_TARGET); ../../packager/units/%(CPU_TARGET)-%(OS_TARGET);. -dLCL -dLCL%(LCL_PLATFORM) memdslaz.pas"/>
</CONFIG>

Project options are:

-MObjFPC -Scghi -O3 -OoREGVAR -Twince -Parm -gs -gl -WG -vewnhi ....

Svn 32410

Thanks, Ludo

It would be good to have a bug report about this with target set to 0.99

Felipe Monteiro de Carvalho wrote

It would be good to have a bug report about this with target set to 0.99

ah, there is already a report =) answered too fast

ah, there is already a report =) answered too fast

Felipe,

If you refer to http://bugs.freepascal.org/view.php?id=20362 then I would suggest I create a new bugreport. The title "WinCE app with the sqlite3laz package wont compile " and the category "[Packages] Database" isn't appropriate at all to track the problem with package compiler settings.

Ludo

I just tested this in a normal win32 environment and the same problem occurs: adding a new package compiles automatically with dwarf info when lazarus build config is set to no debug or to stabs. Project is configured for stabs (my default setting). So the problem is not even related to the cross compile environment.

Ludo

Ludo Brands wrote

Dear list, Since lazarus has changed default debug info to dwarf, packages that are

It has not.
The change was reverted. the default is -g again (which means it may be dwarf, as -g is whatever fpc defaults to for the target)

However, the revert does not fix, any config that was already updated. So if you ever used any of the snapshots or svn versions that included the dwarf2 default, then you config may have been changed.

IMHO, I do not consider it a bug, that a config (which was only created by an experimental, and never released version) is not automatically reverted.

Does that happen, if you start with an empty primary config directory?

As for packages: If any package file has been committed with the dwarf setting, then those files need to be found individually.

It does not on my system.

Maybe time to update again

2011/10/7 Ludo Brands :
Configuring the

lazarus build settings to stabs or no debug doesn't help. Project settings aren't changing anything either. How can I change the default compiler settings for packages? Am I missing something or is this a bug? Other than the dwarf problem, how to compile code without debug info in the packages?

I think you would need to open each .lpk and change the debugging info in it by hand.

I think the options you enter in Build Lazarus Options are applied to each package as well (the $(IDEBuildOptions) macro) and they are applied at the end of the FPC command line. So maybe if you used something like "-g-" in the Build Lazarus Options then it would disable debugging info for all packages? Or "-g-s" would overwrite it to Stabs. I haven't tried that however.

Changelog says that it was reverted in 32468. The original reporter in http://bugs.freepascal.org/bug_view_advanced_page.php?bug_id=20362 used
32543. I can't tell if he used a "default dwarf" before.

Agreed. Only a pity that after the different messages on this list regarding the change to dwarf and its negative consequences, the revert wasn't signaled.

Am the contents of primary config directory. Did a make clean all. Build lazarus from the ide with Debug IDE profile, after reseting dwarf to stabs;). Resulting packages are compiled with -g although I specified -gs. Then rebuild IDE with Optimized IDE. Surprise: packages are still build with -g.
Example: sqlite3laz.compiled:
<?xml version="1.0"?>
<CONFIG>
<Compiler Date="1060328717"
Value="C:\lazarus\fpc\svn\bin\i386-win32\fpc.exe"/> <Params Value=" -MObjFPC -Scgi -O1 -g -gl -vewnhi -l -FuC:\lazarus\ideintf\units\i386-win32
-FuC:\lazarus\lcl\units\i386-win32\win32 -FuC:\lazarus\lcl\units\i386-win32 -FuC:\lazarus\packager\units\i386-win32 -FuC:\lazarus\components\sqlite\ -FUC:\lazarus\components\sqlite\lib\i386-win32\win32\ -dLCL -dLCLwin32 sqlite3laz.pas"/>
</CONFIG>

Cleaned manually the sqlite\lib\i386-win32\win32 but same result.

Still same question for svn 32738: how can I change debug info for packages?

Ludo

I think you would need to open each .lpk and change the debugging info in it by hand.

That is the workaround I suggested for the wince suggestion.

While the Build Lazarus options are -O2 -g- -Xs , sqlite3laz( and all other packages) is compiled with:
sqlite3laz.compiled:
<?xml version="1.0"?>
<CONFIG>
<Compiler Date="1060328717"
Value="C:\lazarus\fpc\svn\bin\i386-win32\fpc.exe"/> <Params Value=" -MObjFPC -Scgi -O1 -g -gl -vewnhi -l -FuC:\lazarus\ideintf\units\i386-win32
-FuC:\lazarus\lcl\units\i386-win32\win32 -FuC:\lazarus\lcl\units\i386-win32 -FuC:\lazarus\packager\units\i386-win32 -FuC:\lazarus\components\sqlite\ -FUC:\lazarus\components\sqlite\lib\i386-win32\win32\ -dLCL -dLCLwin32 sqlite3laz.pas"/>
</CONFIG>

Ludo

2011/10/7 Ludo Brands :

I see it would only work for packages that use <CustomOptions Value="$(IDEBuildOptions)"/> but only some of them use it, like LCL, FCL.

Ludo Brands wrote

Agreed. Only a pity that after the different messages on this list regarding the change to dwarf and its negative consequences, the revert wasn't signaled.

It was, on 23/09/2011 11:07 by me, under the subject "Re: [Lazarus] Spurious package rebuild", in reply to

Clearly missed that one, sorry,

Ludo

Missed that one, sorry.

Ludo

Found the problem: Ide/compileroptions.pp line 1422

  GenerateDebugInfo :=
aXMLConfig.GetValue(p+'Debugging/GenerateDebugInfo/Value', false);
  UseLineInfoUnit :=
aXMLConfig.GetValue(p+'Debugging/UseLineInfoUnit/Value', true);
  UseHeaptrc := aXMLConfig.GetValue(p+'Debugging/UseHeaptrc/Value', false);
  UseValgrind := aXMLConfig.GetValue(p+'Debugging/UseValgrind/Value',
false);
  if aXMLConfig.GetValue(p+'Debugging/DebugInfoType/Value', '') = '' then
begin
    // upgrading old setting
    DebugInfoType := dsAuto;
    if GenerateDebugInfo then
      DebugInfoType := dsStabs;
    if UseLineInfoUnit or UseHeaptrc or UseValgrind then
      GenerateDebugInfo := True; // LineInfo implies debug info
    b := aXMLConfig.GetValue(p+'Debugging/GenerateDwarf/Value', false);
    if b then begin
      GenerateDebugInfo := True;    // The old setting implied this
      DebugInfoType := dsDwarf2Set; // explicit dwarf, upgrade to +set
    end;
UseLineInfoUnit is set to true if no xml data available and a few lines
further it says if UseLineInfoUnit or UseHeaptrc or UseValgrind then
GenerateDebugInfo := True;

So all packages that don't specify debug info are compiled with -g -gl. QED

Remains the question. How to change the package debug info without configuring individual packages? This is making debug/release project management a nightmare.

Ludo