[Lazarus] Compile Error Latest SVN

[Lee Jenkins]

Maxim Ganetsky wrote:
> Lee Jenkins пишет:
>> Mattias Gaertner wrote:
>>> On Fri, 13 Jun 2008 21:33:38 -0400
>>> Lee Jenkins <lee at datatrakpos.com> wrote:
>>>
>>>> Maxim Ganetsky wrote:
>>>>> Lee Jenkins пишет:
>>>>>> Lee Jenkins wrote:
>>>>>>> I updated from latest svn and get the following error:
>>>>>>> M:\lazarusSVN\ide\environmentopts.pp(1536,57) Error: Identifier
>>>>>>> not found "GetUserDir"
>>>>>>>
>>>>>>> Pointing to this portion of EnvironmentOpts.pp
>>>>>>>
>>>>>>> {$IFNDEF Ver2_2_0}
>>>>>>>    AMacroList.Add(TTransferMacro.Create('Home',GetUserDir,
>>>>>>>                   lisUserSHomeDirectory, nil, []));
>>>>>>> {$ENDIF}
>>>>>>>
>>>>>>> Any advise?  Thanks,
>>>>>>>
>>>>>> Sorry, should have mentioned I have fpc 2.2.1
>>>>> Please, update your FPC or use release version (2.2.0).
>>>>>
>>>> Hmmm.  The last svn that I downloaded, 15156 compiled ok with fpc
>>>> 2.2.1 so I'm having trouble understanding why I would want to
>>>> downgrade from 2.2.1 to 2.2.0...
>>> Lazarus only runs with the released FPC or the current development
>>> version. At the moment: 2.2.0 and 2.2.3.
>>>
>>> Mattias
>>>
>> Odd.  As I mentioned, I have rebuilt using 2.2.1 but I guess that particular 
>> source must have changed between the last time I updated.
>>
>> Is there a way to specify an fpc to use for rebuilding lazarus, but use my newer 
>> one to compile my programs or must I just change the paths manually when I want 
>> to build lazarus and then set them back?
> 
> AFAIK no. It won't work anyway as all modules used by your program 
> should be compiled by the same compiler version (your program depends on 
> LCL and Lazarus depends on it too, hence LCL, Lazarus and your program 
> need the same compiler version).
> 
> IMO the best option here is to use 2.2.0 for production software. 2.2.3 
> can be used too, but there can be some unexpected glitches. Also you can 
> try 2.2.2rc1. It is newer than 2.2.0 and should be more stable than 2.2.3.
> 
> BTW if Lazarus doesn't compile with 2.2.0 then you have found a bug.
> 

Yeah, I get the same error using either FPC.

I'll submit a bug report.

Thank you.

-- 

Warm Regards,

Lee