Post a reply to the thread: Patching and compiler variables?
Click here to log in
What's the name of our main installation product (in uppercase letters), directly followed by the current year?
You may choose an icon for your message from this list
Will turn www.example.com into [URL]http://www.example.com[/URL].
Re: Patching and compiler variables? Hello Dave, Fixed in our latest internal source codes. Thank you for bringing this to our attention! Friedrich
Re: Patching and compiler variables?
Re: Patching and compiler variables? Dave, Item in review, thank you.
Patching and compiler variables? The ability to use compiler variables in defining paths to the files (on the compiler's computer) is *extremely* useful. eg Install File [MYFILEDIR]\myFile.exe However it doesn't seem to work for defining the old versions of files to be patched. I'm looking to patch multiple old versions in [MYOLDFILEDIR_1]\myFile.exe [MYOLDFILEDIR_2]\myFile.exe ... But the compiler throws a wobbler: "file not found". It doesn't object with the explicit path there, and I'm pretty sure my compiler variables are correctly defined. Is this a feature of the program or is it just me? Dave Webber PS: I have defined the compiler variables in two stages: [MYOLDFILE_ROOT] = <long path> [MYOLDFILEDIR_1] = [MYOLDFILE_ROOT]\dir1 [MYOLDFILEDIR_2] = [MYOLDFILE_ROOT]\dir2 ... but that seems to work fine in other circumstances.
Patching and compiler variables?
Forum Rules
