in
properly as a new release, really. ([EMAIL PROTECTED] is the author of
ddiwrapper).
--- On Sun, 30/3/08, Detlef Riekenberg [EMAIL PROTECTED] wrote:
From: Detlef Riekenberg [EMAIL PROTECTED]
Subject: Re: DLL exports... HELP?! (wine based win32 printer drivers for
openprinting)
To: Hin-Tak Leung
On Sa, 2008-03-29 at 15:51 +, Hin-Tak Leung wrote:
- The ddiwrapper-hack works only with a very small amount
of self-contained drivers
Yes, but say, a GSOC project for distinguishing which are
self-contained and which are not?
Only Usermode Printer Drivers (w2k and above) can work
(NT4
I have. (I did build the cross-compiler myself, rather than a
downloaded binary).
--- On Wed, 26/3/08, Marcel Partap [EMAIL PROTECTED] wrote:
From: Marcel Partap [EMAIL PROTECTED]
Subject: Re: DLL exports... HELP?!
To: [EMAIL PROTECTED]
Cc: wine-devel@winehq.org
Date: Wednesday, 26 March
I had a better look at the wine 2007 GSOC work - works quite alright, found my
CUPS
spooler; I am surprised that it uses the registry. It builds alright with mingw
cross compiler (I have it around for other stuff and reasonably familiar with
it), but a little surprised that there are a few
Hi Hin-Tak,
no no misunderstanding ;) ...that printer proxy does exactly what the name says: it's only purpose
is to log the calls a printer driver receives from the windows spooler. And yes, somehow some
glitches creeped in ^ ^
The rest of my work - as Detlef has already stated - depends on a
On Mi, 2008-03-26 at 14:47 +, Hin-Tak Leung wrote:
Wow :-). I have almost wanted to suggest such a native wine-based
printer driver
as a linux foundation/openprinting GOSC project (I am one of the
mentors under the
openprinting umbrella
Folks, I've been trying to make a bunch of control panel applets
for wine for some time now.
a CPL is basically a DLL which (the most importnat part) exports a
function called CPlApplet; Without it, the cpl isn't worth a thing.
It is the presence of that export which basically
If you build a wine dll inside the wine source tree we use gcc in combination
with some wine magic for compilation. Exporting of functions in that case
happens through a '.spec' file.
When you want to work outside the wine tree (as it can be more convenient) you
could also use 'winegcc' for
On Wednesday 26 March 2008 12:39:39 pm you wrote:
If you build a wine dll inside the wine source tree we use gcc in
combination with some wine magic for compilation. Exporting of functions in
that case happens through a '.spec' file.
When you want to work outside the wine tree (as it can be
Hi Stefanov,
attached is the code of a standalone proxy DLL I developed last year during SoC, have a look
especially at the makefile for cross-compilation...
regards marcel.
--
div id=signature
Obstacles are those frightful things you see when you take your eyes off your
goal.
the terms of the license you don't mind we do some work based
on your work? I'll let the other printing folks know.
--- On Wed, 26/3/08, Marcel Partap [EMAIL PROTECTED] wrote:
From: Marcel Partap [EMAIL PROTECTED]
Subject: Re: DLL exports... HELP?!
To: [EMAIL PROTECTED]
Cc: wine-devel@winehq.org
11 matches
Mail list logo
