[GEM-dev] Re: [GEM-cvs] Gem/src/Gnu configure.in

james tittle tigital at mac.com
Wed May 25 15:17:21 CEST 2005


On May 24, 2005, at 12:55 PM, IOhannes m zmoelnig wrote:

> james tittle wrote:
>
>> blech....
>>
>> On May 24, 2005, at 2:21 AM, IOhannes m zmoelnig wrote:
>>
>>
>>>
>>> i guess it is like:
>>> paste the code into acinclude.m4
>>> run "aclocal"
>>> run "autoconf"
>>> run "./configure"
>>>
>>
>>
>> ...btw, I figured out why I was getting a spurious "copy.o" in my /
>> Manips makefile:  configure is really, really, really dumb!  In the
>> finder I had duplicated "camera.cpp", which auto names the duplicated
>> file to "camera copy.cpp"...configure then apparently got confused  
>> by  a
>> "name with a space", which really is pathetic in this day and
>> age...again, why is this considered a good build system?
>>
>
> this has nothing to do with autoconf.
> it is just a simple script "makesource" which does "ls *.cpp >>  
> Make.source"
> so you can either blame the script or ls.
>
> a workaround might be using something like
>   ls *.cpp | sed -e 's/ /\\ /g' >> Make.source
> and consider all platforms that do not have "sed" installed to be
> inferior :)

...or at least make 'sed' a requirement for compiling gem ;)

...well, after taking a non-configure way out of the whole sinf()  
defining, I then discovered that I was using some undocumented  
altivec functions that somehow worked :-)  There was an easy solution  
to that...and then there were quite a few other little easy problems  
(mostly to do with compiling files I'd never played with before, like  
the pix_filmNEW stuff), and before ya know it, I was down to the  
linking stage...

...for linking I had to hand enter some makefile stuff, with the end  
result being that it finally compiled, linked, and loaded!  Whew...as  
soon as I can sort things out a bit more here (and test objects  
better), I'll start committing the changes...

jamie




More information about the GEM-dev mailing list