Sergio wrote:
My problem was that the MainDll function in the source lacked << extern "C"
Now my question is: how's it that VC++ did not need that?
Yes.
VC++ Has special handling for DllMain,WinMain and such. Depending on the
different targets you have (MFC COM C and so on) there is di
From: "Sergio" <[EMAIL PROTECTED]>
> Now my question is: how's it that VC++ did not need that?
Maybe it has special handling for main()?
--
Dimi.
cesfully compiled and made work the ones that were written in C.
>
> My question: is this problem related to generating / linking to the .res
> file? Is there a way of solving it? Did anyone here have the same problem
> and manage to make it work? Has anyone here tried to link a C++ project
>
he same problem
and manage to make it work? Has anyone here tried to link a C++ project
using winelib and did not experience this problem?
Thank you very much. I am really lost and your help will be highly
appreciated. Sergio.
Title: Message
Hello
all.
Do you know if there
is a way to compile a shared object
using winelib with g++ or
wineg++ ?
I am using
wine20050725 under Linux2.6.8.1-12mdk
I need references to advapi32.dll and
user32.dll.
Thanks.
Rob D wrote:
The files I cant seem to compile are ones that use std string.
If you are using msvcrt, You cannot use native g++ std with Winelib. In
this case you'll need to grab STLPort. And hack on it to compile over
wine & msvcrt headers. This is for two reason. 1- The headers are
incompatibl
Hi Rob,
>I get a few errors like the following:
>error: ::div has not been declared
>error: ::ldiv has not been declared
div and ldiv may or may not be included in the std namespace. Try
changing the calls to either remove the scope resolution from their
calls or adding std before it.
>And tons
Ive undertaken the task of converting 2 rather large Win32 applications
to run on Solaris 10.
I have managed to tweak nearly all of the files so they will compile
with wine after running winemaker.
The files I cant seem to compile are ones that use std string.
I get a few errors like the following:
Geoff Hart wrote:
In fact, I often wonder why his work (which is very impressive) was
not included in the base? It would
seem ATL/MFC support is a very worthy addition to Wine. Anyone care
to re-discuss why his patches
were rejected?
This is my own fault I never sent them.
I sent them to wine-
r the package to
work using Winelib.
Cool, this would be very valuable indeed.
I agree. Actually, we are doing this also. I started with the work
done by Boaz Harrosh, and found
it helped a great deal (we also are using ATL, __uuidof, etc...).
In fact, I often wonder why his work (whi
Brian Vincent wrote:
On Sat, 22 Jan 2005 13:19:35 -0800, Dan Dennison <[EMAIL PROTECTED]> wrote:
Are there resources available beyond simple compilation tips to assist in
the building of the MFC library under Winelib?
Excellent. Also, does anyone know the (US) legal aspects of this? Is
th
Dan Dennison wrote:
Are there resources available beyond simple compilation tips to assist in
the building of the MFC library under Winelib?
Thanks!
Dan Dennison
[EMAIL PROTECTED]
I have done it up here last year. I did not post any results because by
the time I finished they changed the wineli
On Sat, 22 Jan 2005 13:19:35 -0800, Dan Dennison <[EMAIL PROTECTED]> wrote:
> Are there resources available beyond simple compilation tips to assist in
> the building of the MFC library under Winelib?
Excellent. Also, does anyone know the (US) legal aspects of this? Is
there a EULA that prevent
kage to
> work using Winelib.
Cool, this would be very valuable indeed.
> Are there resources available beyond simple compilation tips to assist in
> the building of the MFC library under Winelib?
All we have is this:
http://winehq.org/site/winelib#atlmfc
--
Dimi.
Hi Dan,
--- Dan Dennison <[EMAIL PROTECTED]> wrote:
> So as a service to the Wine community I plan to document the process of
> building libmfc as part of my master's project. Although the MFC is not the
> focus of this project, porting of it is a requirement for the pac
to document the process of
building libmfc as part of my master's project. Although the MFC is not the
focus of this project, porting of it is a requirement for the package to
work using Winelib.
Are there resources available beyond simple compilation tips to assist in
the building of th
"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
Le lun 18/10/2004 à 08:49, Dimitrie O. Paun a écrit :
> On Mon, Oct 18, 2004 at 03:25:12AM -0400, Ross Quinlan wrote:
> > This generates one new file, "Makefile" (no Makefile.in, configure)
> > so I can't run ./configure --with-wine etc.
>
> Yeap, that's expected. Docu needs updating.
It is (at l
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
On Mon, Oct 18, 2004 at 03:25:12AM -0400, Ross Quinlan wrote:
> This generates one new file, "Makefile" (no Makefile.in, configure)
> so I can't run ./configure --with-wine etc.
Yeap, that's expected. Docu needs updating.
> If I try a simple make, here's the result:
>
> E> make all
> win
Hello,
This is my first try with winelib ...
I'm running RedHat 7.3. I've downloaded the wine source (wine-20040914)
and built everything using ./tools/wineinstall.
I'm trying the winemine example in the winelib doc. I've copied the
.c, .h, and .rc files to a new directory winemine2 and in th
Nikolay A. Liber wrote:
Have anybody tried to use winelib in python modules? I need to make
python bindings to some propritary DLL that available as a binary only.
I made shared library that simply dynamicaly loads that DLL using
winelib mono hack. It works perfectly when I link it with simple
Hi All
Have anybody tried to use winelib in python modules? I need to make
python bindings to some propritary DLL that available as a binary only.
I made shared library that simply dynamicaly loads that DLL using
winelib mono hack. It works perfectly when I link it with simple C test
program
Hi,
--- [EMAIL PROTECTED] wrote:
> - When I run winemaker in my project root directory, it runs
> successfully
> but in
> the end does not produce any configure script as said in the
> documentation
> but
> produces directly a Makefile
I build simple Winelib apps all the time. Try this
winema
Hi,
I have been trying to use Winelib to build a very trivial Windows Application
on
Unix just to test the working of winelib. But it does not work according
to the
documentation at all. Here are the problems I found:
- When I run winemaker in my project root directory, it runs successfully
but
On Fri, Jul 30, 2004 at 11:06:29AM +, James Supancic wrote:
> I need to compile a Windows application under Linux. I need to use dlls and
> Linux librarys. No matter what I try I can't get winegcc to include the
> Linux librarys in the linking stage. What must I do to get winegcc to link
> w
I need to compile a Windows application under Linux. I need to use dlls and
Linux librarys. No matter what I try I can't get winegcc to include the
Linux librarys in the linking stage. What must I do to get winegcc to link
with both the dlls and Linux libs?
Thank you for your time,
James Steven
On Fri, 23 Jul 2004 08:28:16 +0200, Jeroen Janssen wrote:
> Apparently I'm missing some #defines in wine's rpcproxy.h in order to be
> able build the proxy/stub dll?
> For instance:
> PROXYFILE_LIST_START
> PROXYFILE_LIST_END
> REFERENCE_PROXY_FILE
Yes, our rpcproxy.h is missing quite a few impor
Hello,
I was wondering whether there is a wine COM client/server application
that makes use of winelib & widl (to generate a proxy/stub dll).
Apparently I'm missing some #defines in wine's rpcproxy.h in order to be
able build the proxy/stub dll?
For instance:
PROXYFILE_LIST_START
PROXYFILE_LIST_
It seams that I wasn't using the winlib application at all. Instead there
was a left over exe that the launch script was finding and using
No that I tried to rebuilt it I can't get it working. I am getting:
wine: Unhanded exception (thread 0009), starting debugger...
err:seh:start_debugger
On September 14, 2003 02:52 am, Kevin Atkinson wrote:
> OK maybe there not. It was just that stderr was going to stdout. So can
> I safely write binary data to stdout are do I need to somehow turn stdout
> into binary mode to avoid EOL conversion.
Yes, there's no binary mode to enable, things sh
On Sun, 14 Sep 2003, Dimitrie O. Paun wrote:
> On September 13, 2003 08:32 pm, Kevin Atkinson wrote:
> > > > Furthermore it is still using windows I/O.
> > >
> > > Hmm, can you post the Makefile you used to build the thing?
> >
> > Attached is to files. One is for building the application via a c
On September 13, 2003 08:32 pm, Kevin Atkinson wrote:
> > > Furthermore it is still using windows I/O.
> >
> > Hmm, can you post the Makefile you used to build the thing?
>
> Attached is to files. One is for building the application via a cross
> compiler, the other is with Winelib.
OK, I took a
Yes, you can use glibc, but this stdout/err problem maybe related to
something else. Eric is the expert in that area...
the attached patch should fix it
A+
--
Eric Pouech
Index: scheduler/process.c
===
RCS file: /home/cvs/cvsroot/wine/
On Sat, 13 Sep 2003, Dimitrie O. Paun wrote:
> On September 13, 2003 04:03 am, Kevin Atkinson wrote:
>
> > OK I figured out how to get it to compile. I manually created
> > libavisynth_c.def, it is attached. I know that wasn't the best thing to
> > do but it worked. Why is this necessary? Can
On September 13, 2003 04:03 am, Kevin Atkinson wrote:
> OK I figured out how to get it to compile. I manually created
> libavisynth_c.def, it is attached. I know that wasn't the best thing to
> do but it worked. Why is this necessary? Can't it use the .lib file?
> Failing that is there a scrip
On Fri, 12 Sep 2003, Kevin Atkinson wrote:
> Here is what I got:
> avs2yuv4mpeg.cpp - the main program
> avisynth_c.h - header for DLL I need to link with
> avisynth_c.lib - lib "" "
>
> And I want to compile this into an executable avs2yuv4mpeg
OK I figured out how to
41 matches
Mail list logo
