[ros-dev] Autogenerating compiler specific .def files
marc.piulachs at codexchange.net
Sat Dec 1 16:29:59 CET 2007
There is something I still don't see clear, the integration with rbuild.
When we use the tool you are writing with the mingw backend rbuild will
generate the required instructions in the makefile.auto and will be make who
executes it as part of a module compilation, same case as winebuild no
problem here. But when this same tool is used with the MSVC backend will
have to be rbuild who executes it directly as no makefile.auto is generated
in this case. See the problem?
I see 3 possible solutions for it:
- Let MSVC generate the .def file by calling your tool in the pre-build
event. (solution equivalent to the makefile.auto in mingw) it has the
disadvantage of regenerating the def file in every build. Also will require
having the full codebase (your tool included) to build a module with msvc.
- Make it different to winebuild and process all the codebase searching for
.spec files and generate both .def files (gcc and msvc) in the intermediate
folder when called by Makefile in the same sense as buildno or nci tools. It
will be executed only if the files are not present. It's not very elegant.
- Integrate your tool inside rbuild, I'm against adding particular parsers
inside rbuild but we may do an exception here as it seems to me the best
Or may be you have a better solution.
From: ros-dev-bounces at reactos.org [mailto:ros-dev-bounces at reactos.org] On
Behalf Of Colin Finck
Sent: Saturday, December 01, 2007 1:40 PM
To: 'ReactOS Development List'
Subject: Re: [ros-dev] Autogenerating compiler specific .def files
For your information: As there were no more comments on this, I started
working on a tool now, which transforms .spec files into both GNU and MSVC
It will be based a bit on winebuild's code, but won't include all this stuff
we don't need (code generation for non-PE compilers, 16-bit support, etc.),
so it should become more lightweight and faster.
If someone still disagrees with such a solution, please do that now and
Aleksey Bragin wrote:
> 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.
> Aleksey Bragin.
Ros-dev mailing list
Ros-dev at reactos.org
More information about the Ros-dev