24 Nov
2007
24 Nov
'07
7:32 p.m.
Marc, I think I haven't been very clear on this. What I mean, is that
the .spec format already includes *everything* needed to produce
either gcc or msvc-format .def file. So no point in creating yet
another format. Nothing more nothing less, that's what I ment.
I'm glad to hear disadvantages of that way.
WBR,
Aleksey Bragin.
On Nov 24, 2007, at 7:01 PM, Marc Piulachs wrote:
There is absolutely no need to invent yet another
format for storing
export functions. It was invented once by MSVC, it was invented by
GCC/MinGW, both are incompatible, it was invented by Wine to have
ability of easy functions stubbing. Should there be another invention
of the same wheel by ReactOS now?
If GCC/MinGW wouldn't be that *strange*, it
could stdcall-fixup, and
then properly link, this way .def could be created in the lowest
common denominator format.
That's the problem I'm trying to solve..:) The point on this change
is not
really store them in xml inset of plain text, is not that
important, for me
there are two reasons, first declare this information so rbuild can
manipulate it as objects and apply checking , logic , whatever ...
and the
most important store the information on a neutral , compiler
agnostic and
rich format that allow us to generate (export to) ANY format we
desire out
of it. Currently def files are tided to mingw which is bad.
At the end the information must be there so what's the difference
between
having it in a file with extension .def or .spec and having it on a
file
with .rbuild extension? IMO It's not reinventing the wheel
/Marc