I port the application on MacOS X, but NMAKE is used in the original build system of the developer, and ideally they would like to keep it instead of switching to a new one.
I managed to run NMAKE under OSX using wines (built using MacPorts) and add Objective-C support for build files and create a Unix-related run.exe PE shell that the wine can load, but uses POSIX to call back on things like gcc and ld, as described in various places online, as a means of exiting wine back to Unix.
However, I have a few specific problems. They are imperfect enough that I can work with the port, but this means that I need to sometimes run assemblies several times because of the time.
Basically, when wine.exe accesses the shell and therefore gcc, the connection between the child processes seems to be broken. gcc and ld will never return an error code even if they fail because they cannot get the exit code from their children. ar actually prints out, he won’t be able to find his child and return immediately, which will cause problems when ld tries to link object files to libraries that are still compiled.
Has anyone else tried something similar and seen the same problem, on OSX or elsewhere? Is there an obvious solution?
source
share