On 2008.05.08., at 15:05, Alex Strickland wrote:
Szakáts Viktor wrote:
Also for non-GNU BCC/VC builds ace32.lib is automatically
generated based on ace32.dll, if found (exact path displayed
at build time), but if you have multiple versions of ace32.dll
on your system, the one found by the buil
Szakáts Viktor wrote:
Also for non-GNU BCC/VC builds ace32.lib is automatically
generated based on ace32.dll, if found (exact path displayed
at build time), but if you have multiple versions of ace32.dll
on your system, the one found by the build process might be
different from the one your appl
Hi Marek,
I still don't agree with you on this.
To build rddads.lib someone will need the ACE
package from (now) Sybase installed. This package
has the .h and the .dll (the one to be distributed
with the final apps!). Harbour build process will
find both the header and the .dll and build the
RDD
Hi,
> The problem here is that ace32.dll (found at runtime)
> and ace32.lib (used at link time) is mismatched.
>
> For best results it's good to have ace32.dll, ace32.lib
> and ace.h matched at compile time of rddads.lib and link
> time of final app, and later ace32.dll and the final
> applicatio
Hi Ed,
The problem here is that ace32.dll (found at runtime)
and ace32.lib (used at link time) is mismatched.
For best results it's good to have ace32.dll, ace32.lib
and ace.h matched at compile time of rddads.lib and link
time of final app, and later ace32.dll and the final
application kept mat
