For ALL projectsRequire_FileQ,filename
Simply, this copy file from Source--System32 to Target--System32
Syntax only designed to copy 1 File.
Require_FileQ,filename + %PluginArch%
%PluginArch% values can be x86 or Empty.
If you are creating a 32bit application plugin that naturally requires 32bit version of clbcatq.dll , than :
If you are creating a multi architecture plugin (Generally 32bit + 64bit application, like 7-Zip plugin), than :
On NT6x Require_FileQ also adds associated .mui files.
On NT6x Require_FileQ, have en-US fallback feature for mui files (If local mui not found, en-US mui checked..)
On NT6x if file(s missing) Require_FileQ only gives warning, see Reply74 here http://theoven.org/index.php?topic=541.msg11412#msg11412
NEVER use folder name
(it may look working but it is NOT...)
Require_FileQ created for max speed for most common (system32/syswow64) single file requirements,
adding such options will slow down significantly...
such folder thingy only required by project specific plugins (like Core or Component plugins),
where direct commands can be used more effectively (faster cleaner)
You can find such usage examples on many Components plugins
Do NOT use with Wildcards (? and/or *) (neither Require_FileQ )
Reason behind not having wildcard support on Require_FileQ:
* adding such support to Macro Library would result with very much speed down.
* it can not be achived with wb syntax as common easly
* even if demanded highly, Require,WildCard can be added, but only 2 or 3 lines requires such thing overall for common plugins.
Advice: So far using direct commands used on plugins that requires wildcard, follow the known path ;).
* Rare Special Case :
Advanced plugin authors - Project specific or Personal Plugins :
If for some reason you require both version of a file in a single plugin (mostly in project specific plugins)