I want add Another little problem for ads ace32.dll ver 9 is able to connect only a v9 server and superior if any ace32.dll ver 8 is able to connect only a v8 server and superior ace32.dll ver 7 is able to connect only to a v7 server and superio ace32.dll ver 6 is able to connect only ti a v6 server and superior So if you have a customer with 6 one with 9 ,ecc you must generate multiple version or be limited to v6 feature particularry v9 allow Visual Fox Pro format and will be usefull integrate it
Is possible generate from multiple acesdk dir? Consider this particularry for binary distribution simple to use 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 > >
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
