Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2012-07

Building lhelp.... and primary config path

2 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Reinier Olislagers

Hi Mattias & list,

In testing with my fpcup installer, I've noticed that the lhelp build gets kicked off on the fly sometimes when I press F1 on a keyword.

Very nice!

However, I also noticed it doesn't seem to pick up my (non-default) primary config path but uses the default (i.e.
C:\Users\Reinier\AppData\Local\lazarus\ on my Vista box).

I tried to reproduce this using a snapshot on a clean Windows machine but couldn't get the lhelp compile to work by just pressing F1 on a keyword.... because it is delivered as a precompiled .exe

So, just wanted to know if primary config path of the current IDE taken into account when kicking off the lhelp build?
If you (probably Mattias...) don't know by heart, I'd be happy to dig deeper and find out myself!

On a related note: would it make sense to distribute lhelp compiled with default instead of debug mode (i.e. with no or external debug symbols)? This would reduce size from about 20 meg to about 3 meg on a Windows machine...
(Don't know if it is considered better to have a larger exe where you can get a backtrace, but a patch is attached if wanted)

Thanks,
Reinier
-------------- next part --------------
Index: components/chmhelp/lhelp/lhelp.lpi
=================================================================== --- components/chmhelp/lhelp/lhelp.lpi (revision 37920) +++ components/chmhelp/lhelp/lhelp.lpi (working copy) @@ -153,6 +153,10 @@
</Optimizations>
</CodeGeneration>
<Linking>
+ <Debugging>
+ <GenerateDebugInfo Value="False"/>
+ <UseExternalDbgSyms Value="True"/>
+ </Debugging>
<Options>
<Win32>
<GraphicApplication Value="True"/>

Reply by email

Mattias Gaertner
to Reinier Olislagers
Show quoted text 17 lines
Hi Mattias & list, In testing with my fpcup installer, I've noticed that the lhelp build gets kicked off on the fly sometimes when I press F1 on a keyword. Very nice! However, I also noticed it doesn't seem to pick up my (non-default) primary config path but uses the default (i.e. C:\Users\Reinier\AppData\Local\lazarus\ on my Vista box). I tried to reproduce this using a snapshot on a clean Windows machine but couldn't get the lhelp compile to work by just pressing F1 on a keyword.... because it is delivered as a precompiled .exe So, just wanted to know if primary config path of the current IDE taken into account when kicking off the lhelp build?

yes. chmhelppkg which compiles lhelp uses the current lazarus directory.

Show quoted text 9 lines
If you (probably Mattias...) don't know by heart, I'd be happy to dig deeper and find out myself! On a related note: would it make sense to distribute lhelp compiled with default instead of debug mode (i.e. with no or external debug symbols)? This would reduce size from about 20 meg to about 3 meg on a Windows machine... (Don't know if it is considered better to have a larger exe where you can get a backtrace, but a patch is attached if wanted)

The deb and rpm strip the lhelp exe. The windows snapshot should do the same.

Mattias

Reply by email