Forum > Suggestions
Build Release
ca70du:
Hello!
I'd like to suggest a new menu item: "Build Release" under "Execute". Action: build a release executable, without any or with minimum debug info. I think it's a more intelligent way than the current "build mode". The IDE may always build debug mode, except under "Build Release".
Also, in "Project Options", under "Compiler Options", a new item: "Release", with release-specific options, such as an optional "Release path" to store release builds, and the option to include version number to executable's file name. So the "Build modes" may be excluded.
Att.,
Carlos E. S. M.
Curitiba / Paraná / Brazil
lucamar:
People use "buld modes" for much more than a simple Debug/Release dichotomy: cross compilation, for example, or building various executales with different options/defines, etc.
So you see how your proposal would basically constraint everyone for little, if any, gain: it's so easy to change modes! And you can do almost everything you want through mode-specific options so ... what's the point?
My 2 cents. :)
ASBzone:
--- Quote from: ca70du on August 21, 2018, 09:25:44 pm ---I'd like to suggest a new menu item: "Build Release" under "Execute". Action: build a release executable, without any or with minimum debug info. I think it's a more intelligent way than the current "build mode". The IDE may always build debug mode, except under "Build Release".
--- End quote ---
You seem to be asking for a pre-built "build mode".
It seems to me that you can achieve what you desire by using the Build Modes, in combination with "Run --> Compile many Modes..."
I started using that recently to build x32 and x64 Windows executables in a single selection. I also used it on a test program to generate 4 executables (main, main-mini, main64, main64-mini) with differing configuration, so that I could quickly validate changes.
If I could set a default for which of the checkboxes in "Compile many Modes..." were selected by default, I would be ecstatic, but an extra click or two hasn't killed me yet...
Martin_fr:
You can set a diff output directory in each build mode. So that is solvable.
You can also set the build modes as defaults for all new projects.
There may be a point, to have those defaults pre-configured in new lazarus installs.
Leledumbo:
--- Quote from: Martin_fr on August 21, 2018, 10:53:43 pm ---There may be a point, to have those defaults pre-configured in new lazarus installs.
--- End quote ---
Kinda agree with this one, sometimes we're too advanced that we think everything is as intuitive as it can be for everyone.
Attached is my style, might not fit everyone's standard as I like to make the directory layout somewhat more organized:
--- Code: ---project.lpi
src
+ here lies your .pas / .pp, may be broken further down into plain unit files, forms, libraries, whatever according to your taste
lib
+ debug
+ <fpctarget>
+ here lies your .ppu / .o / .rst / .res, etc. files using debug options
+ release
+ <fpctarget>
+ here lies your .ppu / .o / .rst / .res, etc. files using release options
bin
+ debug
+ here lies the executable using debug options
+ release
+ here lies the executable using release options
--- End code ---
Navigation
[0] Message Index
[#] Next page