so you have a separate project to compile the windows library . . . .
Look . . I am not saying your way is wrong, but my way is less time consuming assuming I don't have a naming conflict. If it is too much trouble for Dr Hipp to change the single name that is causing the problem, then so be it, but the arguments about obscure development environments and ignoring valid way to compile simply is not valid. I also notice that there has been some confusion by Dr Hipp in mixing up the operating systems asserting that I am compiling for OS9 (I noticed that the email I sent to Dr Hipp and published by him on the list has a portion of my words edited from macosx to Mac).
I also labour under the 4D API plugin architechture which prefers that i do it in this.
. . . . . . I am much more interested in getting the Open command bug getting fixed.
On 07/09/2004, at 10:34 AM, Will Leshner wrote:
On Sep 6, 2004, at 7:27 PM, Jeff Edwards wrote:
There is also the question of compiling for windows with the same source, but not the same library on the OSX machine.
Actually, I do use the same source. I just make a Windows library in CodeWarrior.
