Hi list,

Was looking at what changed in the post 1.0 configs to see if fpcup needs to be adjusted.

Ran fpcup with empty primary config path dir to get and let fpcup setup Lazarus trunk, then ran Lazarus and converted to new format.

Noticed this difference in fpcdefines.xml:
directly after fpcup ran:
<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:
1. Should I be worried about this ;)
2. What does InPath mean?

Thanks,
Reinier

The InPath is the ppc executable in PATH (the environment variable). It is used by the fpc executable, which is normally used. If this changes the IDE asks the compiler for its settings.

Mattias

Huh? So the fpc.exe in a different directory outside the path uses a ppc exe in the path???

Shouldn't fpc.exe look for e.g. ppc386.exe in its own directory?

Or do I misunderstand you?

Thanks,
Reinier

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.

Or do I misunderstand you?

Mattias

Ok, fair enough, thanks!