On Fri, Jul 25, 2003 at 03:41:10PM +0100, E Lea wrote:
>
> >E> I'm playing around with a program that controls a small "design
> >E> cutter" - it's basically a plotter that connects via the parallel
> >E> port.
> >
> >E> There is some Windows CAD software that knows about the plott
--- Jon Bright <[EMAIL PROTECTED]> wrote:
> Should I understand from this that Wine should build under Cygwin?
> Certainly, it doesn't here - there's a series of errors related to
> functions with the @suffixes...
>
> If it's supposed to build, I can happily supply the errors in question...
99
Hello,
On 22 Jul 2003, Vincent [ISO-8859-1] Béron wrote:
> Le mar 22/07/2003 ŕ 12:43, Peter Hanecak a écrit :
> >
> > while building Wine on "RedHat 8"-like system I encountered two typos in
> > Wine documentation which prevented me from "compiling" documentation with
> > jade (openjade-1.3.1-
Hello again,
On Fri, 25 Jul 2003, Peter Hanecak wrote:
> On 22 Jul 2003, Vincent [ISO-8859-1] Béron wrote:
>
> > Le mar 22/07/2003 ŕ 12:43, Peter Hanecak a écrit :
> > >
> > > while building Wine on "RedHat 8"-like system I encountered two typos in
> > > Wine documentation which prevented me f
"Jon Bright" <[EMAIL PROTECTED]> wrote:
> > will need to do anyway). Wine makefiles already have all the needed
> > tweaks to strip stdcall @xx suffixes when building under MinGW or Cygwin.
>
> Should I understand from this that Wine should build under Cygwin?
It has some problems (notably for n
>E> I'm playing around with a program that controls a small "design
>E> cutter" - it's basically a plotter that connects via the parallel
>E> port.
>
>E> There is some Windows CAD software that knows about the plotter and
>E> sends commands to it, as far as I can tell in one of
Hi,
Dmitry Timoshkov wrote:
will need to do anyway). Wine makefiles already have all the needed
tweaks to strip stdcall @xx suffixes when building under MinGW or Cygwin.
Should I understand from this that Wine should build under Cygwin?
Certainly, it doesn't here - there's a series of errors rel
> "E." == E Lea <[EMAIL PROTECTED]> writes:
>>...
E.> [ppdev] "378" = "/dev/parport0"
E.> [ports] "read" = "0x779,0x378,0x379,0x280-0x2a0" "write" =
E.> "0x779,0x378,0x379,0x280-0x2a0"
E.> in my ~/.wine/config
E.> Should this be enough to get it working? Or does the
"Jonathan Wilson" <[EMAIL PROTECTED]> wrote:
> > Only native Win32 compilers do that. gcc under Linux doesn't generate
> > that crap.
> aah, I was using MingW on windows to test the dll.
You can use Wine build system in order to test your dll. For that you
just need to make your new dll a part of
"Jonathan Wilson" <[EMAIL PROTECTED]> wrote:
> the MS Cards.dll is complled with "the dll does the cleanup" set to on
> (i.e. its using retn xx instructions).
That's how pascal (stdcall) calling convention works.
> When I compile it, i get the @nn on the end of the names.
Only native Win32 com
the MS Cards.dll is complled with "the dll does the cleanup" set to on
(i.e. its using retn xx instructions).
When I compile it, i get the @nn on the end of the names.
This is a problem since cards.dll exports the names without the @nn
How do I set things up in my .spec file?
>
>E> 2) The second method is a direct connection to LPT1.
>E> With Wine, in the first case I get a message in a dialog box saying
>E> the call to "StartDocPrinter" failed and
>E> fixme:winspool:StartDocPrinterA (hPrinter=0x1, Level=0x1,
>E> pDocInfo=0x408a28dc): stub
>E> to
12 matches
Mail list logo
