[Lazarus] Building and starting Lazarus on Raspberry Pi2 with Raspbian Jessie

[Mark Morgan Lloyd]

Bo Berglund wrote:
> On Fri, 16 Oct 2015 06:39:24 +0000, Mark Morgan Lloyd
> <markMLl.lazarus at telemetry.co.uk> wrote:
> 
>> I simply used the standard 1.4 sources. And I'm pretty sure I've already 
>> told you that.
> 
> Will Lazarus 1.4.x work with FPC 3.1.1?
> Or do I have to scrap all of what I have done and start over?

Try it, I don't think there will be problems.

Different Lazarus versions generally have a compiler version they 
assume, but at present they're running neck-and-neck.

>>>> $ svn ls http://svn.freepascal.org/svn/lazarus/tags
>>>> ..
>>>> lazarus_1_4/
>>>> lazarus_1_4_2/
>>>> lazarus_1_4_4/     <--- Most recent
>>>> lazarus_1_4_RC1/
>>>> lazarus_1_4_RC2/
>>>> lazarus_1_4_RC3/
> 
> I guess I would need 1.4.4 then, or is that what you get from 1.4?

Those are distinct tagged versions. Assume that 1_4 in that context is 
1.4.0, that there were three release candidates for review, and that the 
later ones are elsewhere labelled "fixes".

>> The problem with Subversion is that the revision number and tagged 
>> releases are distinct, so except in the case of trunk it's difficult to 
>> say "get 1.4.4, then step back one revision".
>>
>> In the case of trunk (looking at an arbitrary machine here)...
>>
>> $ cd /usr/local/share/lazarus-trunk
>> $ svn info
> 
> Here is what I currently have in the lazarus dir:
> pi at rpi2-jessie ~/development/lazarus $ svn info
> Path: .
> Working Copy Root Path: /home/pi/development/lazarus
> URL: http://svn.freepascal.org/svn/lazarus/trunk
> Relative URL: ^/trunk
> Repository Root: http://svn.freepascal.org/svn/lazarus
> Repository UUID: 4005530d-fff6-0310-9dd1-cebe43e6787f
> Revision: 50059
> Node Kind: directory
> Schedule: normal
> Last Changed Author: juha
> Last Changed Rev: 50059
> Last Changed Date: 2015-10-14 18:39:48 +0200 (Wed, 14 Oct 2015)
> 
> So I am on trunk...
> 
>> # Step back one revision:
>> $ svn up -r 40412
> 
> OK, that is when you use the revision number, what about the tag name?

You're on trunk. There is no tag name.

> I have googled for how to move to a particular Subversion tag (aka
> branch).

NO. THEY ARE DISTINCT. DO NOT GO THERE.

> I found this webpabe:
> http://svnbook.red-bean.com/en/1.1/ch04s05.html

That's the standard book. Start at the beginning rather than jumping in 
at the middle and guessing.

> When trying to understand the concept I wound up with this command:
> 
> svn switch http://svn.freepascal.org/svn/lazarus/lazarus_1_4_4
> 
> Executed inside the already checked out trunk copy, would this get me
> to the tag lazarus_1_4_4?
> 
> Or is it better to just delete the development/lazarus dir and then do
> a checkout from development? Like this:
> cd /home/pi/development
> rm -r lazarus
> svn co http://svn.freepascal.org/svn/lazarus/lazarus_1_4_4 lazarus
> cd lazarus
> make clean bigide

Stick to distinct tags or to trunk. I say again:

'The problem with Subversion is that the revision number and tagged 
releases are distinct, so except in the case of trunk it's difficult to 
say "get 1.4.4, then step back one revision".'

> Last question:
> I have seen different suggested locations for lazarus here.
> 
> Juha suggested:
> ~/development/lazarus
> 
> but your example shows:
> /usr/local/share/lazarus-trunk
> 
> and the tutorial I started with uses:
> /usr/local/lazarus
> 
> This confuses me a lot, what is the "standard" way of locating
> programs like Lazarus (and fpc for that matter)?

There isn't one. Even considering "standard packages", different Linux 
distreaux and other unix implementations (Solaris etc.) have different 
conventions for where they install non-core stuff: /usr/local, /opt, 
/opt/local and so on.

/In/ /general/, you can rely on /usr/local/bin being on your path, or 
it's safe to add it. So basically, you can install both FPC and Lazarus 
wherever you want, and put symlinks in /usr/local/bin for the programs 
you need most.

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

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