<div><br></div>Im trying to build a simple winelib. Its not working and is returning 'error 127'. I have some question:<div><br></div><div>(1) how do i determine which functions are exported by wine? All i see using nm <a href="http://zmq.dll.so">zmq.dll.so</a> is the names of my proxy function (add_proxy) instead of the name that is going to be called by the windows program (add)</div>
<div>(2) whats the point of a spec file? what im saying is that i can build my files without a spec file and no error message is produced. In what stage of building is the spec file actually used?</div><div>(3) is there any way to debug just specifically the errors produced by my stub dll under wine? somehow specify a debug channel where the real reason for 'error 127' is? The stub dll being dynamically loaded by a program for which i have no source code.�</div>
<div><br></div><div>I am using these simple test files:</div><div>//in zmq.c</div><div><div>#include "zmq.h"</div><div>#include "wine/debug.h"</div><div>#include <windef.h></div><div><br></div><div>
long WINAPI add_proxy(long a,long b) {</div><div>�� �return a+b;</div><div>}�</div></div><div>;;in zmq.dll.spec</div><div>@ �stdcall add( long long ) add_proxy</div><div><br></div><div><br></div><div>and then i do</div><div>
<br></div><div><div>winegcc -c � � �-o zmq.o zmq.c</div><div>winegcc -shared -o <a href="http://zmq.dll.so">zmq.dll.so</a> zmq.o�</div></div><div><br></div><div>However, i notice that i can just get rid of the spec file and no error</div>
<div>messages are produced which makes no sense since the dll is supposed to redirect calls to add to add_proxy.</div><div><br></div><div>And once i use the windows program to call function add, i get the 'error 127', which means it cant find the function 'add.'</div>
<div><br></div><div><br></div><div><br></div>