Hi,
> I think we have this, but with dll's we didn't use the lib prefix which
> also
> worked, but probably with static we need the lib prefix. We will update
> our
> build files tomorrow and try with the lib prefix.
With lib prefix and static linking the exception test as part of ACE does
work.
Hi,
> > Seems -static doesn't work yet for ACE. When I create the ACE.dll,
> and want
> > to link it with an executable using -static, which files do I now
> need? Ld
> > complains that it can't find -lACE, do I need ACE.a, ACE.lib?
>
> If you create dynamic / shared libraries / dlls, then the wa
On Sun, 2009-05-17 at 09:55 +0200, Johnny Willemsen wrote:
> > I think I mixed two options at our side. I am retesting with just -
> > static at
> > this moment.
>
> Seems -static doesn't work yet for ACE. When I create the ACE.dll, and want
> to link it with an executable using -static, which fil
Hi,
> I think I mixed two options at our side. I am retesting with just -
> static at
> this moment.
Seems -static doesn't work yet for ACE. When I create the ACE.dll, and want
to link it with an executable using -static, which files do I now need? Ld
complains that it can't find -lACE, do I need
Hi,
I think I mixed two options at our side. I am retesting with just -static at
this moment.
Johnny
> I am trying to use -static to workaround the exception problem. When I
> now
> create our own library (ACE), what is the file extension that it should
> use?
> We have now .a but that doesn't w
Hi,
I am trying to use -static to workaround the exception problem. When I now
create our own library (ACE), what is the file extension that it should use?
We have now .a but that doesn't work when linking our executable that uses
that ACE lib. I can start experimenting, but maybe someone has used
