[Lazarus] FPCDefines.xml: RealCompiler InPath

Reinier Olislagers reinierolislagers at gmail.com
Sun May 13 10:41:44 CEST 2012


On 13-5-2012 10:37, Mattias Gaertner wrote:
> On Sun, 13 May 2012 10:18:37 +0200
> Reinier Olislagers <reinierolislagers at gmail.com> wrote:
> 
>> On 13-5-2012 9:28, Mattias Gaertner wrote:
>>> On Sat, 12 May 2012 11:13:16 +0200
>>> Reinier Olislagers <reinierolislagers at gmail.com> wrote:
>>>>       <RealCompiler File="C:\development\fpc\bin\i386-win32\ppc386.exe"
>>>> Date="1085035464" OS="win32" CPU="i386"
>>>> InPath="C:\development\fpc\bin\i386-win32\ppc386.exe" FullVersion="2.6.1"/>
>>>> after conversion:
>>>>       <RealCompiler File="C:\development\fpc\bin\i386-win32\ppc386.exe"
>>>> Date="1085035464" OS="win32" CPU="i386"
>>>> InPath="C:\development\fpcbootstrap\ppc386.exe" FullVersion="2.6.1"/>
>>>>
>>>> The InPath location is different.
>>>> Note that c:\development\fpcbootstrap is in my path and contains ppc386.exe
>>>> c:\development\fpc\bin\i386-win32 is not in my path.
>>>>
>>>> Questions:
>>>> 2. What does InPath mean?
>>>
>>> The InPath is the ppc executable in PATH (the environment variable).
>>> It is used by the fpc executable, which is normally used.
>> Huh? So the fpc.exe in a different directory outside the path uses a ppc
>> exe in the path???
> 
> Yes.
> 
>  
>> Shouldn't fpc.exe look for e.g. ppc386.exe in its own directory?
> 
> First it searches in the -XP, then it its own directory and finally in
> PATH.
> 
> I fixed the search order in the codetools.
>  
Ok, fair enough, thanks!





More information about the Lazarus mailing list