Gentlefolk ... please ... how may I join the Winforms cabal?
<Wayne.Arenz <at> gd-ais.com>
2004-03-16 20:19:54 GMT
Assuming the
misunderstandings of February have been resolved and there is now a definite
direction for Mono-Wine-Winforms, could someone please post and / or e-mail me
rather explicit directions for how to build the latest -- even if imperfect --
Mono-Wine-Winforms solution? As I look through the message threads,
go-mono compile instructions, etc., I have to admit to (newbie) confusion
re:
a) pre-requisites --
should there be a pre-install of Mono and/or Wine before
building?
c) pre-requisites --
Peter indicated the one patch in CVS along with his readme, and then attached
another patch or two in his Winforms-list message. I also note ROUGE Alain
mentions an mcs-0.30.patch. What is the complete set of patches to be
applied, and to what source? What is the source for that source?
(whose CVS servers?).
d) final "baking"
... make what, in what order, and using what make
flags?
e) Where does the
CVS folder \mono\mcs\class\System.Windows.Forms\WINELib ... the "stub" ... fit
into things, if at all?
f) Whatever else one
needs to know ... what foot to stand on while doing this, what phase of the
moon, what day of the week ... we all know that it's "magic" that holds code
together, so I'd really like to know this particular magic.
Finally, it would be
**great** if the tutorial could instruct how it might be done on a SPARC machine
(if Winforms can work on mono-mint). However, it will be **just fine** if
the tutorial could instruct me sufficiently that I could pull this
off on my new 2.8 GHz/Intel/SuSE laptop.
****Bottom
line: I'd like to be on "the bleeding edge", and I don't mind bleeding a
little -- but I'd prefer not having to bleed to death. :)
****
R. Wayne
Arenz
GENERAL
DYNAMICS
Advanced Information
Systems
E-mail: wayne.arenz <at> gd-ais.com
Phone : 937-427-7274
2673 Commons Blvd, Suite 200
Beavercreek, OH 45431