[Lazarus] RC1 from svn, and lhelp

[Mark Morgan Lloyd]

Mark Morgan Lloyd wrote:
> I'm trying to build and minimally-exercise RC1 for various platforms, I 
> might be some time. Below are observations that apply to multiple targets.
> 
> I notice that when IDE startup changes the Lazarus directory etc., that 
> it leaves the path to the lhelp binary unchanged. So after changing a 
> system from lazarus-trunk to lazarus-1.0-rc1, the options still refer to 
> the lhelp binary in the lazarus-trunk tree. I presume that this is 
> fixable by putting a macro in the path.

$LazarusDir() works fine here. Noted that this is a case where there 
isn't a dialog(ue) to select a directory or binary, but I think it would 
be useful if the IDE could detect when it was being asked to store 
something relative to its own directory and asked the user whether to 
collapse this into a macro.

> I notice that you can't build the documentation using e.g.  make chmdocs 
>  as part of the same operation as the rest of the IDE, since it assumes 
> that the path to the lazarus directory has already been corrected. The 
> correct sequence is to get the sources via svn, make bigide, run IDE to 
> correct paths and then make chmdocs.
> 
> When lhelp comes up in response to F1 on a keyword, the left pane only 
> shows the database relevant to that keyword. While other databases can 
> be opened successfully, showing the names of all available databases as 
> soon as lhelp comes up would make it look more complete.

Hitting F1 over a different category of keyword correctly adds the 
database to the left-hand pane.

lhelp in RC1 doesn't automatically shut down when the IDE does. I think 
I've seen this working in the past, but I've just checked and a 
fairly-recent trunk similarly misbehaves.

> While the LCL/IDE help is building, there are many messages of the form
> 
> Warning: Target ID of <link> is unknown: "#rtl.Classes.TStrings"
> Warning: Target ID of <link> is unknown: "#rtl.Classes.TStrings.Text"
> 
> Do these represent a permanent problem which should be reported as an 
> error, or will the links be automatically resolved once the RTL database 
> is available?

-- 
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]