"Boaz Harrosh" <[EMAIL PROTECTED]> wrote:
> >[...] so I'm curious where all of the time is spent.
> Most definitely the Linux-shared loader. It took ages. The code is heavy
> C++ code full of templates with weak symbols, inline virtual functions,
> and plain horizontal code structure. almost any th
Eric Frias wrote:
Thanks for the suggestion! Even if it isn't elegant, it sounds like it will
work (and is very close to what we were doing with the older wine). I might
even be able to coax our build system into generating all of the *_export()
and using_dlls() functions automatically.
Yes I
From: "Boaz Harrosh" <[EMAIL PROTECTED]>
> <>Not happy and is a bit out of dated but it Looks it could still work
> today.
> [...]
Thanks for the suggestion! Even if it isn't elegant, it sounds like it will
work (and is very close to what we were doing with the older wine). I might
even be able
Eric Frias wrote:
Does anyone have a solution they're happy with?
<>Not happy and is a bit out of dated but it Looks it could still work
today.
Do a .spec file for each C++ dll with one c function like:
void mydll_export( )
{
}
// you need real code + .spec declaration
In your app or in the dl
"Jia L Wu" <[EMAIL PROTECTED]> wrote:
> It seems that I have to write a spec file for each dll to import(and
> export) functions provide by other dlls. However, since they all written
> in c++ and what need to be imported can either be class or class method,
> and parameters can be class either. SO
Hi,
I have a win32 program written in C++. I am trying to port it to linux
using winelib. The software contanis one exe file and several dll files. I
would like to keep this structure when moving them to linux. That is, I
still would like to generate several corresponding shared libraries
(instead
