On 21/06/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I think this can be explained by the order of the options. Compare the results of what
you see when you click on the "Show Options" button in the compiler options.
OK, I did that. As show below. As you can see in the first example,
Lazarus decided to add the -o switch and use the same patch as the -FU
switch. Effectively the same as the -FE switch. Exactly my problem!!
// specified the Unit output directory only.
-S2cgi -OG1 -gl -WG -vewnhi -l
-Fu/opt/lazarus/lcl/units/i386-linux/
-Fu/opt/lazarus/lcl/units/i386-linux/gtk/
-Fu/opt/lazarus/packager/units/i386-linux/
-Fu.
-FUddd/
-oddd/project1
-dLCL
-dLCLgtk
In this example you can see there is no -o switch added by Lazarus,
which means it works as expected, when you specify the -FU Only
controlling the output path of the units and not the exe.
// specified the -FU switch in Other tab only.
-S2cgi -OG1 -gl -WG -vewnhi -l
-Fu/opt/lazarus/lcl/units/i386-linux/
-Fu/opt/lazarus/lcl/units/i386-linux/gtk/
-Fu/opt/lazarus/packager/units/i386-linux/
-Fu.
-FUddd
-dLCL
-dLCLgtk
So the exact *bug* is now highlighted. Lazarus is specifying the ouput
exe path with the -o switch when we didn't ask it to. The Project
Options -> Target executable was left blank and only the Unit output
directory was specified, yet Lazarus decided to specify the target
executable anyways.
The -o switch should only be set if the Project Options -> Target
executable is specified.
Graeme.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
