Re: abicollab/win32 why not use libabiword-builder?

Robert Staudinger wrote:
>
> On 6/4/07, Jordi Mas <jmas@softcatala.org> wrote:
>
> [...]
>
>> The current build system has to do with VC support as you can see in
>> win32.mk.
>> As far I understand (correct me if I'm wrong), with the new buildsys
>> we are
>> dropping this support completely.
>>
>> > What would it take to support VS in the new (autofoo) buildsys?
>>
>> I'm not buildsys expert. I cannot tell. The result should that with
>> builsys
>> you should be able to build with mingw and vc.
>>
>> Let me know if you have more questions. And thanks for the great
>> effort that
>> you are doing with buildsys.
>
> Several approaches seem feasible:
> (1) Turn the current diving make build into a separate "builder"
> module, for those who want to build using VC.
> (2) Drop support for commandline builds on win32, someone would have
> to maintain the VC project.
> (3) Fridrich pointed out that VC's compiler works with autotools under
> cygwin and that OOo is using that (possibly Mozilla does the same).
> (4) Investigate whether inkscape's custom win32 build tool "btool"
> (modelled after java's Ant build tool) works with VC.
>
> What do you think? Personally I'm leaning towards (2), if that'd be
> feasible (because it's least intrusive IMO).

I am inclined to agree that the VC should be supported through a VC
project file. If the whole point of supporting VC is because it is a
decent development tool, then that seems like the only sensible option.
Maintaining the project file is not a big deal once it is initially set
up, and there should be (possibly rather outdated) project file in the svn.

Tomas
Received on Tue Jun 5 16:54:36 2007