Hi Massimo, You got stuck in an infinite loop, and just increasing the noise I'm afraid.
I've explicitly covered this specific problem in my mail on Apr 1 (but it wasn't a joke), with a three lines which does actually work, but, you apparently *still* didn't read it. Sorry to say, but this really raises the question if it's worth answering at all. Brgds, Viktor On Fri, Apr 17, 2009 at 7:39 PM, Massimo Belgrano <mbelgr...@deltain.it>wrote: > I continue documenting what i have discovered: > > c:\devl\acesdk>dlltool -d ace32.def -D ace32.dll -l libace32.a -k -v > dlltool: Processing def file: ace32.def > dlltool: LIBRARY: ACE32.dll base: ffffffff > dlltool: Processed def file > dlltool: Processing definitions > dlltool: Processed definitions > dlltool: Creating library file: libace32.a > dlltool: run: as -o dcbfh.o dcbfh.s > dlltool: No such file or directory > dlltool: CreateProcess > > > 2009/4/15 Massimo Belgrano <mbelgr...@deltain.it>: > > i have posted a messages on sysbase ads follow reply > > -------------------------------------------------- > > What part doesn't work? I have never used MinGW, so I do not have > specific > > knowledge there. But maybe if you indicate what error you are seeing, we > > can provide some direction. Do the tools give an error? Is the .def > file > > invalid? Or is the resulting lib file invalid in some way? I don't > think > > ACE32.DLL has any unusual properties. It is simply Win32 DLL with a > bunch > > of exported functions. I would assume you have looked at the following > > page, but if not, maybe it will provide some help: > > http://oldwiki.mingw.org/index.php/CreateImportLibraries. > > > > Mark Wilkins > > Advantage R&D > > > > > > 2009/4/14 Viktor Szakáts <harbour...@syenar.hu>: > >> Hi Massimo, > >>> > >>> Hi Vicktor > >> > >> [ It's Viktor with a 'k', or it's fine with a 'c' too, 'ck' is quite > >> strange. ] > >> I'm not sure what you're trying to do, I've posted my three lines > >> of commands in the message you replied to, but you've been > >> trying with different dlltool command. Correct it. > >> As I wrote even these three lines won't create usable implib, > >> you probably need to manually edit the .def file, but don't ask > >> me how. I suggest to contact the vendor of this lib to give > >> information on MinGW compatibility/usage. It's an expensive > >> product, probably they have some sort of support and maybe > >> this issue already appeared in their history. > >> Brgds, > >> Viktor > >> On Tue, Apr 14, 2009 at 11:36 AM, Massimo Belgrano < > mbelgr...@deltain.it> > >> wrote: > >>> > >>> Hi Vicktor > >>> I am not able to generate valid libace32.a becasue is zero lenght > >>> wich version do you use? > >>> i copyed pexport.exe and dlltool in c:\devl\acesdk > >>> cd \devl\acesdk > >>> del libace32.a > >>> pexports ace32.dll > ace32.def > >>> set oldpath=%path% > >>> set PATH=%~dp0 > >>> dlltool -d ace32.def -D a > >>> > >>> > >>> This is my version > >>> GNU dlltool (GNU Binutils) 2.19.1 > >>> PExports 0.43 Copyright 1998, Anders Norlander Changed 1999, Paul > >>> Sokolovsky > >>> > >>> > >>> 2009/4/1 Viktor Szakáts <harbour...@syenar.hu>: > >>> > It worked for me after massaging it a bit: > >>> > --- > >>> > set PATH=%~dp0 > >>> > pexports ace32.dll > ace32.def > >>> > dlltool -d ace32.def -D ace32.dll -k -l libace32.a > >>> > --- > >>> > The ugly PATH trick is needed because dlltool tries to > >>> > run 'as' tool and it only finds it if in PATH, even if they are > >>> > in the same and current dir :) > >>> > The other ugly bit is that pexports is missing from > >>> > several MinGW distros, notably the latest ones, which > >>> > are unofficial. > >>> > So, for now this routine will have to be done by > >>> > users locally. > >>> > The third bit is that I didn't manage to use libace32.a > >>> > to actually link a Harbour executable. [ Same missing > >>> > symbols. ] > >>> > Brgds, > >>> > Viktor > >>> > On Wed, Apr 1, 2009 at 6:11 PM, Massimo Belgrano < > mbelgr...@deltain.it> > >>> > wrote: > >>> >> > >>> >> I have posted question on sysbase ng of ads > >>> >> on internet i have found > >>> >> http://es.groups.yahoo.com/group/t-gtk/message/1462 > >>> >> > >>> >> > >>> >> > http://objectmix.com/xharbour/241009-rddads-ace32-import-libraries-mingw32.html > >>> >> In not read on yahoo group > >>> >> >1.- Vamos a extraer de la dll, por ejemplo ace32.dll, las > >>> >> > definiciones: > >>> >> >c:\>pexports ace32.dll > ace32.def > >>> >> >Digamos, que pexports seria lo mismo que la herramienta impdef. > >>> >> >2.- Despues vamos a crear la libreria libace32.a, a partir del > fichero > >>> >> >de definiciones. > >>> >> >c:\>dlltool -d ace32.def -D ace32.dll -k -l libace32.a > >>> >> >3.- Despues, tenemos que añadir la libreria a nuestro makefile. > >>> >> >-lace32 > >>> >> > >>> >> 2009/4/1 Viktor Szakáts <harbour...@syenar.hu> > >>> >>>> > >>> >>>> Do you think to a solution that allow same hbmk2 syntax working in > >>> >>>> either enviroment? > >>> >>>> HBMK2 my.PRG ace32.lib rddads.lib -GUI -GTWVT -GTWVG -m -w0 > >>> >>>> -omio.exe > >>> >>> > >>> >>> Yes, I prefer this whereever possible. In your example you > >>> >>> should use '-lrddads' to be compiler neutral. With ace32, > >>> >>> we will see, I think MinGW should find the lib by using -lace32, > >>> >>> given that ace32.dll is placed in the lib path. But for me it then > >>> >>> complains about all missing symbols, so in the case of ace32, > >>> >>> something more needs to be done. > >>> >>> Please try to get information from the internet or from Advantage, > >>> >>> as I won't be able to deal with this (I'm no ace32 user). If > >>> >>> something useful can be done with this in hbmk2, I'll try to > >>> >>> to implement it. > >>> >>> Brgds, > >>> >>> Viktor > >>> >>> > >>> >>> _______________________________________________ > >>> >>> Harbour mailing list > >>> >>> Harbour@harbour-project.org > >>> >>> http://lists.harbour-project.org/mailman/listinfo/harbour > >>> >>> > >>> >> > >>> >> > >>> >> > >>> >> -- > >>> >> Massimo Belgrano > >>> >> > >>> >> Analisi e sviluppo software per Lan e Web - Consulenza informatica - > >>> >> Formazione > >>> >> Delta Informatica S.r.l. http://www.deltain.it/ +39 0321 455962 > >>> >> > >>> >> _______________________________________________ > >>> >> Harbour mailing list > >>> >> Harbour@harbour-project.org > >>> >> http://lists.harbour-project.org/mailman/listinfo/harbour > >>> >> > >>> > > >>> > > >>> > _______________________________________________ > >>> > Harbour mailing list > >>> > Harbour@harbour-project.org > >>> > http://lists.harbour-project.org/mailman/listinfo/harbour > >>> > > >>> > > >>> > >>> > >>> > >>> -- > >>> Massimo Belgrano > >>> > >>> Analisi e sviluppo software per Lan e Web - Consulenza informatica - > >>> Formazione > >>> Delta Informatica S.r.l. http://www.deltain.it/ +39 0321 455962 > >>> _______________________________________________ > >>> Harbour mailing list > >>> Harbour@harbour-project.org > >>> http://lists.harbour-project.org/mailman/listinfo/harbour > >> > >> > >> _______________________________________________ > >> Harbour mailing list > >> Harbour@harbour-project.org > >> http://lists.harbour-project.org/mailman/listinfo/harbour > >> > >> > > > > > > > > -- > > Massimo Belgrano > > > > Analisi e sviluppo software per Lan e Web - Consulenza informatica - > Formazione > > Delta Informatica S.r.l. http://www.deltain.it/ +39 0321 455962 > > > > > > -- > Massimo Belgrano > > Analisi e sviluppo software per Lan e Web - Consulenza informatica - > Formazione > Delta Informatica S.r.l. http://www.deltain.it/ +39 0321 455962 > _______________________________________________ > Harbour mailing list > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour >
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
