Re: [ros-dev] Autogenerating compiler specific .def files

[Marc Piulachs]

>  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

On Nov 24, 2007, at 4:36 PM, Marc Piulachs wrote:

>   I wouldn't use .spec files for several reasons,
> first of all is  
>  that it
>  violates the way how rbuild currently works. Rbuild reads xml  
>  documents in a
>  custom format and produce different outputs depending on various  
>  conditions.
>  IMO rbuild shouldn't be extended to parse anything else but  
>  just .rbuild
>  files.
>
>  Also, winebuild from the rbuild point of view is not different from  
>  any
>  other compiler , so I think the problem is just the opposite ,  
>  rbuild should
>  use the information stored in it's rbuild file to produce the spec  
>  file in
>  addition to the specific def file (it shouldn't be produced by  
>  winebuild
>  anymore) as both files are required to compile wine module XYZ.
>
>  Having the information in rbuild files has also other advantages,  
>  the most
>  important is that it would allow us to use the conditional logic to  
>  export
>  functions based on a given condition, for example hacks like
>  /lib/debugsup.rbuild won't be necessary anymore.
>
>  I wouldn't fork winebuild.
>
>  Regards,
>  Marc 
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev