I am at the first stages of setting up my winelib development, and am attempting to build a simple app (named "type").
Mkefile generated by winemaker creates type.exe.so; where I would expect either type.exe or simply type. What am I missing?
tia, cedar
From: "cdr" cedar@3web.net
Mkefile generated by winemaker creates type.exe.so; where I would expect either type.exe or simply type. What am I missing?
Is the Makefile using winegcc to compile the app? If so, you should get 'type' as the executable.
Dimi Paun wrote:
From: "cdr" cedar@3web.net
Mkefile generated by winemaker creates type.exe.so; where I would expect either type.exe or simply type. What am I missing?
Is the Makefile using winegcc to compile the app? If so, you should get 'type' as the executable.
Yes. ("type.c" is a simple program from Petzold's book). pertinent (I believe) lines from Makefile are:
.. EXES = type.exe .. type_exe_MODULE = type.exe .. ### Generic targets
all: $(SUBDIRS) $(DLLS:%=%.so) $(EXES:%=%.so) ... $(type_exe_MODULE).so: $(type_exe_MODULE).dbg.o $(type_exe_OBJS) $(CC) $(type_exe_LDFLAGS) -o $@ $(type_exe_OBJS) $(type_exe_MODULE).dbg.o $(type_exe_LIBRARY_PATH) $(DEFLIB) $(type_exe_DLLS:%=-l%) $(type_exe_LIBRARIES:%=-l%)
...
(as if winemaker assumes I am trying to buils a shared library?)
In any case, tahnk you very much for your help cedar
From: "cdr" cedar@3web.net
$(CC) $(type_exe_LDFLAGS) -o $@ $(type_exe_OBJS)
What is CC set to?
Dimi Paun wrote:
That's fine it's supposed to do so. But it's also supposed to create a 'type' executable too (a batch file really).
This is where I was (obviously) confused, all I can say in my defence is that Winelib User's Guide in "Getting started" implies that:
(... You are done! Now you can start the application as ./notepad2 ...)
And there is no mention of script that runs ...so - so I was expecting self-contained Linux binary.
That's all fine. You should get type.exe.so (correct, we need that) and a type executable that basically does
wine type.exe.so
I take it that means all winelib-ported apps are NOT true linux binaries - but some half-breed between win32 binaries and Linux binaries? What is then the advantage of porting (using winelib) as opposed to running win32 binaries under wine?
Thank you very much for your help.
cedar
From: "cdr" cedar@3web.net
That's fine it's supposed to do so. But it's also supposed to create a 'type' executable too (a batch file really).
This is where I was (obviously) confused, all I can say in my defence is that Winelib User's Guide in "Getting started" implies that:
(... You are done! Now you can start the application as ./notepad2 ...)
And there is no mention of script that runs ...so - so I was expecting self-contained Linux binary.
Well, the statement above is still correct. And yeah, you don't have to worry about any script -- you just do ./notepad2 :) Why do you care it's a script?
That's all fine. You should get type.exe.so (correct, we need that) and a type executable that basically does
wine type.exe.so
I take it that means all winelib-ported apps are NOT true linux binaries - but some half-breed between win32 binaries and Linux binaries? What is then the advantage of porting (using winelib) as opposed to running win32 binaries under wine?
They are true Linux binaries (ELF format) but they need a bit of setup (for Windows compat) _before_ they start.
But yeah, running the Win32 (PE) executables instead is a true possibility, same speed, etc. But having a Winelib port allows you to better integrate with the Unix env, which may be what you want for a 'true' Linux app.
Dimi Paun wrote:
They are true Linux binaries (ELF format) but they need a bit of setup (for Windows compat) _before_ they start.
Am I correct in assuming (see above in thread) that in some previous wine version it *was* possible to produce stand-alone version? Any plans to make it possible (again)? Perhaps for limited win32 functionality (graphics/GUI event handling only, no device access, registry, etc.?)
But yeah, running the Win32 (PE) executables instead is a true possibility, same speed, etc. But having a Winelib port allows you to better integrate with the Unix env, which may be what you want for a 'true' Linux app.
Should one expect read/write access to memory-mapped files to be faster if it is native Linux? (I must say I am impressed by the fact that Win32 memory-mapped file access works as well under wine as it does).
cdr
From: "cdr" cedar@3web.net
Am I correct in assuming (see above in thread) that in some previous wine version it *was* possible to produce stand-alone version?
Maybe, but if so, it's sooo back in the dark ages that's not worth mentioning.
Any plans to make it possible (again)?
Yes, but don't hold your breath -- it's a difficult problem.
Perhaps for limited win32 functionality (graphics/GUI event handling only, no device access, registry, etc.?)
Something like that :)
Should one expect read/write access to memory-mapped files to be faster if it is native Linux? (I must say I am impressed by the fact that Win32 memory-mapped file access works as well under wine as it does).
No, it should be the same speed. Do you experience any slowdown?
On Thu, 2005-06-16 at 17:04 +0000, cdr wrote:
Dimi Paun wrote:
That's fine it's supposed to do so. But it's also supposed to create a 'type' executable too (a batch file really).
This is where I was (obviously) confused, all I can say in my defence is that Winelib User's Guide in "Getting started" implies that:
(... You are done! Now you can start the application as ./notepad2 ...)
And there is no mention of script that runs ...so - so I was expecting self-contained Linux binary.
That's all fine. You should get type.exe.so (correct, we need that) and a type executable that basically does
wine type.exe.so
I take it that means all winelib-ported apps are NOT true linux binaries - but some half-breed between win32 binaries and Linux binaries? What is then the advantage of porting (using winelib) as opposed to running win32 binaries under wine?
Thank you very much for your help.
cedar
Hmm, once I finish tackling the User's guide (Brian just sent me the work he did on the Winecfg section that still needs to be polished), it might be a very good idea to nearly rewrite the Winelib guide, particularly the intro. Is anyone else working on this at the moment, or is it basically an open task?
I think I'll add it to my wiki page amongst the list of other general usability tasks I have lined up. I hope I get to them this summer ;)
Thanks, Scott Ritchie
From: "Scott Ritchie" scott@open-vote.org
Hmm, once I finish tackling the User's guide (Brian just sent me the work he did on the Winecfg section that still needs to be polished),
Cool, let us know how it goes. Now that Alexandre switch the config to winecfg, it can go in.
might be a very good idea to nearly rewrite the Winelib guide, particularly the intro. Is anyone else working on this at the moment, or is it basically an open task?
Yes, it is an open task. Would ge _great_ if you can tackle it.
-
cdr -
Dimi Paun -
Scott Ritchie