On 2021-12-14 10:29, Bo Berglund via lazarus wrote:
On Mon, 13 Dec 2021 22:44:16 +0100, Bart via lazarus
< snip >
(You might want a "Release and copy to svn" build mode with the
"Execute after command", sou you can also test your release mode build
(if you use e.g. different optimizations, some yet unnoticed bug may
crop up.)
Thanks, I went there and found where I could add the release mode.
I did not even need to enter a copy command because I could set the
"Target
filename" for Release to include the subdirectory bin.
So now my Default mode saves the executable to the project dir and the
Release
saves to subdir bin.
This is exactly what I needed, thanks for explaining it! :)
< snip >
Just FYI, I usually put in the "Target filname" this :
bin\$(TargetCPU)-$(TargetOS)\$(BuildMode)\projectname
and in the "Unit output directory" this :
lib\$(TargetCPU)-$(TargetOS)\$(BuildMode)
The result is that I have a dir structure dependent on OS, CPU and
BuildMode values .
i.e.
CPU=i386
OS=win32
BuildMode=debug
bin\i386-win32\debug with lib\i386-win32\debug
CPU=i386
OS=win32
BuildMode=release
bin\i386-win32\release with lib\i386-win32\release
CPU=x86_64
OS=win64
BuildMode=test_for_scm
bin\x86_64-win64\test_for_scm with lib\x86_64-win64\test_for_scm
etc
regards,
--
Dimitrios Chr. Ioannidis
--
_______________________________________________
lazarus mailing list
lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus
