Warren_Baird/[EMAIL PROTECTED] writes:
> I don't suppose there's any documentation around anywhere talking about
> exactly what the assembly code in winebuild is trying to accomplish, and
> why it can't be done in C? I'm afraid that my assembly is rough enough
> that I haven't been able to fi
(BTW, apologies for the Firewall/CSI thing in my previous message's
"From:" line - they've been mucking about with our external mail server,
and it messed something up - Hope people didn't get bounces if they tried
replying directly - hopefully it'll be fixed for this message.)
Alexandre Jullia
Firewall/[EMAIL PROTECTED] writes:
> I guess my main question is: why is so much assembly needed there - can
> some or all of it be replaced by C code (at least on platforms where you
> never need to interact with real windows libs - like sparc/solaris and
> pa-risc/hpux)?
I'm afraid I won't be a
Firewall/[EMAIL PROTECTED] writes:
> I guess my main question is: why is so much assembly needed there - can
> some or all of it be replaced by C code (at least on platforms where you
> never need to interact with real windows libs - like sparc/solaris and
> pa-risc/hpux)?
No, pretty much ever
Hi all,
As I mentioned in a previous post, I'm
working on getting winelib to run on an HP-UX / PA-RISC system. The
biggest problem I'm facing right now is dealing with all of the assembly
code that is put into the .spec file by winebuild. I'm not an expert
at assembly of any form, and I know ab
