Pour info , dans le fichier ide_compiler il y a ça en plus, si quelqu'un peut le traduire ça m'avancerait
Pour l'instant je copie les ajouts tel quel (en anglais), au bon emplacement, histoire de ne rien oublier.
@Bold "Request Administrator mode for Windows Vista" (Windows only)
@LineBreak
The created exectutable will always be started with administrator rights on Windows Vista.
(it will not launch if the administrator password is not entered). This option should be set
for programs that need to access restricted folders or restricted areas of the registry to get
full access.
@LineBreak
If this option is turned on, the @ReferenceLink "ide_debugger" "standalone debugger" will automatically
selected when debugging, so the program can be tested in administrator mode.
@LineBreak
@LineBreak
Note: This option has no effect when the program is run on other versions of Windows.
@LineBreak
@LineBreak
@Bold "Request User mode for Windows Vista" (Windows only)
@LineBreak
This option disables the "Virtualisation" feature for this executable on Windows Vista. Virtualisation
caused file and registry access to be redirected to a special user folder if the user does not have
the needed rights to do the operation. (this is done for compatibility with older programs)
@LineBreak
Note that this redirection is done without notifying the user which can lead to some confusion if he tries to find
saved files on the filesystem. Because of this, it is recommended to disable this feature
if the program complies with the Windows Vista file/registry access rules.
@LineBreak
@LineBreak
Note: This option has no effect when the program is run on other versions of Windows.
It cannot be combined with the "Administrator mode" option above.
@Bold "Linker options file"
@LineBreak
A textfile can be specified here with further commandline options that should be passed to the linker
when creating the executable. The file should contain one option per line.
@Section Compile/Run
This section contains options that affect how the executable is run from the IDE for testing.
Except for the tools option, they have no effect when the "Create executable" menu is used.
@LineBreak
@LineBreak
@Bold "Enable Debugger"
@LineBreak
This sets the debugger state (on/off) for this source code, or if the main file option
is used, for that file too. This can also be set from the debugger menu.
@LineBreak
@LineBreak
@Bold "Use selected Debugger"
@LineBreak
This allows to choose a different @ReferenceLink "ide_debugger" "debugger type" for this file only.
If this option is disabled, the default debugger is used which can be specified in the
@ReferenceLink "ide_preferences" "preferences".
@LineBreak
@LineBreak
@Bold "Executable Commandline"
@LineBreak
The string given here will be passed as the commandline to the program when running it from the IDE.
@LineBreak
@LineBreak
@Bold "Current directory"
@LineBreak
The directory specified here will be set as the current directory for the program when running it from the IDE.
@LineBreak
@LineBreak
@Bold "Create temporary executable in the source directory"
@LineBreak
With this option turned on, the temporary executable file for running the program from the IDE will be
placed inside the source directory. This can be useful if the program depends on files inside the source
directory for testing. With this option turned off, the executable is created in the systems temporary directory.
@LineBreak
@LineBreak
@Bold "Execute tools"
@LineBreak
Here @ReferenceLink "ide_externaltools" "external tools" can be enabled on a per-source basis.
The "Global settings" column shows if the tool is enabled or disabled in the
@ReferenceLink "ide_externaltools" "tools configuration". A tool will only be executed for the source
if it is both enabled globally and for this source.
@LineBreak
@LineBreak
Note: For a tool to be listed here, it must have the "Enable Tool on a per-source basis" option
checked in the @ReferenceLink "ide_externaltools" "tools configuration" and be executed by a trigger
that is associated with a source file. (ie not by menu or editor startup for example)
@Section Constants
In this section, a set of special editor constants as well as custom constants can be defined
which will be predefined when compiling this source.
@LineBreak
@LineBreak
@Bold "#PB_Editor_CompileCount"
@LineBreak
If enabled, this constant holds the number of times that the code was compiled (both with "Compile/Run" and
"Create Executable") from the IDE. The counter can be manually edited in the input field.
@LineBreak
@LineBreak
@Bold "#PB_Editor_BuildCount"
@LineBreak
If enabled, this constant holds the number of times that the code was compiled with "Create Executable" only.
The counter can be manually edited in the input field.
@LineBreak
@LineBreak
@Bold "#PB_Editor_CreateExecutable"
@LineBreak
If enabled, this constants holds a value of 1 if the code is compiled with the "Create Executable" menu or
0 if "Compile/Run" was used.
@LineBreak
@LineBreak
@Bold "Custom constants"
@LineBreak
Here, custom constants can be defined and then easily switched on/off through checkboxes.
Constant definitions should be added as they would be written within the sourcecode.
This provides a way to enable/disable certain features in a program by defining a constant here and then
checking in the source for it to enable/disable the features with
@ReferenceLink "compilerdirectives" "CompilerIf/CompilerEndIf".
@LineBreak
@LineBreak
Inside the definition of these constants, environment variables can be used by specifying them
in a "bash" like style with a "$" in front. The environment variable will be replaced in the constant
definition before compiling the source. This allows to pass certain options of the system that the
code is compiled on to the program in the form of constants.
@LineBreak
@LineBreak
Example: #Creator="$USERNAME"
@LineBreak
Here, the $USERNAME will be replaced by the username of the logged in user on Windows systems. If
an environment variable does not exist, it will be replaced by an empty string.
@LineBreak
@LineBreak
Note: To test within the sourcecode if a constant is defined or not, the @FunctionColor "Defined"()
@ReferenceLink "compilerfunctions" "compiler function" can be used.
%COMPILECOUNT : replaced with the value for the #PB_Editor_CompileCount constant.
@LineBreak
%BUILDCOUNT : replaced with the value for the #PB_Editor_BuildCount constant.
