Re: [Module::Build] Re: CBuilder vs Windows update

[Randy W. S. <Ra...@Th...>]

On 1/4/2004 12:12 AM, Ken Williams wrote:

> 
> On Saturday, January 3, 2004, at 11:59  AM, Randy W. Sims wrote:
> 
>> I was wondering though... How attached to the interface are you? 
>> Couldn't we shorten the names to the obvious:
>>
>> preprocess() => converts .xs to .c
>> compile()    => converts .c to .o
>> prelink()    => generates export symbol file
>> link()       => creates library or executable (depending on args)
> 
> 
> Yeah, sounds good to me.  I'd had the library/executable split at the 
> compilation stage (compile_library() vs. compile_executable()) though, 
> is that wrong?  When I do "gcc -o foo myprog.c" to create a 'foo' 
> executable, what are the equivalent separate compile & link stages?

I think for the most part that the differences are small enough that we 
can use a parameter to differentiate instead of using seperate routines. 
I'm not yet sure how the static builds will fit in yet. After I get the 
Windows code cleaned up, I'll think about this some more and see if I 
can come up with a more coherent proposal.

> Also, you think we should add XS capabilities to CBuilder?  That would 
> add a lot of extra "smarts" to the module that I'm not sure it really 
> needs.

I hadn't really looked yet at what would be required; I was thinking it 
would just be a simple proxy for invoking xsubpp or EU::ParseXS. It 
seems like it belongs in CBuilder as it is a preprocessor used in 
generating extensions...

> I've got a new (well, actually about 10 years old) machine in my 
> basement that I'm going to set up, among other things, as a project 
> server for stuff like this.  All my modules will have accessible 
> CVS/Perforce/Subversion/whatever repositories on it so we can work a 
> little more effectively on stuff like this.

Ouch! I've got one of those 10+ year old machines sitting around too. It 
was my first PC, though I had had other computers. Hasn't been turned on 
in about 4-5 years, but I haven't been able to bring myself to get rid 
of it. A machine that old should be able to run fine for cvs though if 
your running under linux. It'll probably be more reliable than 
sourceforge. :-)

Randy.