Environment variables
TMP or TEMP Specifies the directory where the temporary files will
be created.
Default: C:\TEMP
EDITOR The name of the preferred text editor.
IDALOG Specifies the name of the log file. Everything appearing
in the message window will be dumped there.
Default: none
IDALOG_SILENT Suppress all output to the message window.
If the IDALOG variable is set, messages will continue to
be written to the log file. Otherwise, they will be lost.
IDADIR Specifies the IDA directory.
Default: the directory where IDA executable is located
IDA_LOADALL The selected loader will load all segments without asking
IDAUSR Specifies the directory for user-specific settings.
Default: Windows: %APPDATA%/Hex-Rays/IDA Pro
Linux: $HOME/.idapro
Mac OS X: $HOME/.idapro
This variable can contain multiple paths, in which case they must
be separated by the platform's path separator character (i.e., ';'
on Windows, and ':' on Linux & Mac OS X.)
NOTE: Using %IDAUSR% for loading plugins.
%IDAUSR% will be considered when scanning for plugins: for
each directory component of %IDAUSR%, IDA will iterate on
files in its "plugins" subdirectory, in alphabetical order.
Plugins with the same case-insensitive file name (without
extension) are considered to be duplicates and are ignored;
only the first plugin with a given name will be considered.
Thus, let's say %IDAUSR% is set to "C:\my_idausr", and a file
"C:\my_idausr\plugins\DWARF.py" exists, then
"C:\my_idausr\plugins\DWARF.py" will be picked up first while
"%IDADIR%\plugins\dwarf.dll" will be considered conflicting,
and thus ignored.
In addition, in each directory, IDA first looks for plugins
with the native extension (e.g., ".dll" on Windows) and only
then looks for files with extensions corresponding to
extension languages (e.g., ".idc", ".py", ...)
Consequently if two files, say "foo.dll" and "foo.py", are
present in the same directory, "foo.dll" will be picked first,
and "foo.py" will be considered conflicting, and thus ignored.
NOTE: Using %IDAUSR% for overriding configuration.
%IDAUSR% will be considered when looking for configuration
files, after the config file found in %IDADIR%\cfg has been
read.
After %IDADIR%\cfg\<filename> has been read & applied, for
each directory component of %IDAUSR%, IDA will look for
cfg/<filename> in it, and, if found, read & apply its
contents as well.
This enables users to have their own small, fine-tuned
configuration files containing just the bits they wanted to
override, stored in one (or more) folder(s) of their choosing.
NOTE: Using %IDAUSR% for specifying themes
%IDAUSR% will be considered when scanning for themes: for
each directory component of %IDAUSR%, IDA will iterate on
subdirectories in its "themes" subdirectory.
NOTE: Using %IDAUSR% for providing additional loaders, processor
modules, .til files, .sig and .ids files
%IDAUSR% will also be considered when building the list of
existing loaders, processor modules, .til, .sig and .ids files.
The following directories will be inspected:
%IDAUSR%\loaders
%IDAUSR%\procs
%IDAUSR%\til\<arch-name>
%IDAUSR%\sig\<arch-name>
%IDAUSR%\ids\<platform-name>Last updated
Was this helpful?