Hi Gerrit,
"Gerrit P. Haase" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
> Hallo Alex,
>
> >>> Since libstdc++ is also static, it will be a fair race if both
> >>> times the static archive is used.
>
> >> libstlport_cygwin.a works fine.
>
>
> >> I tried to do the same thing with mi
Hallo Alex,
>>> Since libstdc++ is also static, it will be a fair race if both
>>> times the static archive is used.
>> libstlport_cygwin.a works fine.
>> I tried to do the same thing with mingw.
> [...]
>> c++ -shared -o ...
> This is wrong, you must also link with -mno-cygwin flag to get
Hallo Alex,
>> Since libstdc++ is also static, it will be a fair race if both
>> times the static archive is used.
> libstlport_cygwin.a works fine.
> I tried to do the same thing with mingw.
[...]
> c++ -shared -o ...
This is wrong, you must also link with -mno-cygwin flag to get the
right
Hi Gerrit,
"Gerrit P. Haase" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
> Hallo Alex,
>
> I've recompiled the STLport library now, it seems that it doesn't work
> with the DLL, when I link against the static library it works:
>
>
> > == 7. File bar.cpp -> Run : BEGIN ==
>
Hallo Alex,
I've recompiled the STLport library now, it seems that it doesn't work
with the DLL, when I link against the static library it works:
> == 7. File bar.cpp -> Run : BEGIN ==
> $ bar_orig
> PARAM1 = (ABCD)
> PARAM2 = (12345)
> PARAM3 = (XYZ)
> $ bar_port
> PARAM1 = (ABCD)
> P
"Alex Vinokur" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
>
[snip]
>
> # File foo.cpp can be seen in attachment
>
[snip]
File foo.cpp can be seen in attachment to _this_ posting.
Sorry.
--
=
"Gerrit P. Haase" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
[snip]
> There are some useful switches for the compiler / linker. You can specify
> the include directory to be used during compilation with:
>
> -I/path/to/stlport-headers
>
> and the path to the libraries you want t
Hallo Alex,
> There is some advance.
> I put the stlport libraries in /lib.
> $ g++ -c -o foo.o foo.cpp
> $ g++ -o foo_port.exe foo.o -lstlport
If you use g++ to link, libstdc++ will be linked in automatically,
that was the reason why I wrote:
gcc -o your.exe your.o -L/your/path -lstlport
> $
"Alex Vinokur" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
> Hi Gerrit,
>
> "Gerrit P. Haase" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
> > Hallo Alex,
> >
> > Am Freitag, 31. Oktober 2003 um 19:41 schriebst du:
> >
> >
> > > "Gerrit P. Haase" <[EMAIL PROTECTED]>
9 matches
Mail list logo
