Hi,

1. Attached patch changes the build lazarus dialog, so that the compiler executable selected in the environment options dialog is used for compilation. Please note that therefore the EnvironmentOpts unit is used in the implementation.

2. Recently the function TBuildLazarusOptions.CompiledUnitExt is added. This function returns .ppw for target_os is win32. This is only true if the compiler is 1.0.x series, not the later series. fpc 1.9 and later also have .ppu for windows. I don't know if lazarus already knows which compiler version is used (I suppose it does) and where it is stored, so I can't send you a patch for this issue.

Regards,
Vincent Snijders.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: gz00045.gz
Type: application/octet-stream
Size: 401 bytes
Desc: "buildlazarus.patch.gz"
Url : http://localhost/pipermail/lazarus/attachments/20031116/e0ed6309/gz00045.obj

Good idea.

Please note that therefore the EnvironmentOpts unit is used in the implementation.

I did it with a parameter.

2. Recently the function TBuildLazarusOptions.CompiledUnitExt is added. This function returns .ppw for target_os is win32. This is only true if the compiler is 1.0.x series, not the later series. fpc 1.9 and later also have .ppu for windows.

Thanks. I didn't know that.

I don't know if lazarus already knows which compiler version is used (I suppose it does) and where it is stored, so I can't send you a patch for this issue.

The codetools were the only part of the IDE, that need to know. So, it was somewhat hidden.
It's amazing how different fpc 1.0.x and fpc 1./9 are, and how irrelevant this is for an IDE.
Implemented.

Although there still are some places left, where the .ppw files are searched.

Mattias