From: "Dimitrie O. Paun" dpaun@rogers.com Hi folks,
As we discussed here a few weeks ago, there is good reason to have a windres compatible mode for wrc.
<snip>
That being said, what would it take to (1) keep the current wrc behavior, and (2) make it compatible with windres?
Here is an alternative idea for dealing with command-line incompatibility: create a link 'windres' pointing to 'wrc'. In the program, we could determine how the program was invoked and handle the command-line options accordingly.
This should technically work, unless we find some reason to 'mix' command line options, in which case we we would have to start 'blending' the two syntaxes. Please note that I am not familiar with the command line options of either program.
<snip>
The modification will typically be: -WINDRES=windres +WINDRES=wrc
WINDRES would not have to be changed using this method.
-- Jeff S.
_________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail
On December 5, 2002 10:51 am, Jeff Smith wrote:
This should technically work, unless we find some reason to 'mix' command line options, in which case we we would have to start 'blending' the two syntaxes. Please note that I am not familiar with the command line options of either program.
If there more many conflicts, I'd agree with you, but ATM at the moment it looks real simple to just mix the commands (that is, also support windres commands in wrc).
<snip>
The modification will typically be: -WINDRES=windres +WINDRES=wrc
WINDRES would not have to be changed using this method.
Creating a symlink is orthogonal to this problem. Even if we mix the commands, we can still create the symlink, but I don't think it's really necessary. In fact, we shouldn't probably do it, as windres can be compiled to exists on Linux also.
On Thu, Dec 05, 2002 at 09:51:18AM -0600, Jeff Smith wrote:
Here is an alternative idea for dealing with command-line incompatibility: create a link 'windres' pointing to 'wrc'. In the program, we could determine how the program was invoked and handle the command-line options accordingly.
I like this hack much better than the previous one :)
Ciao Jörg -- Joerg Mayer jmayer@loplof.de I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.