[geos-devel] Python/Swig/Configure Bug

[Mark Cave-Ayland]

On Thu, 2007-08-30 at 02:20 -0600, Charlie Savage wrote:
> > Actually... am I right in thinking that SWIG is only needed if
> > --enable-python or --enable-ruby is specified? 
> 
> Good point.
> 
> Yes and no.  Remember that we check the SWIG wrapper files into SVN so 
> that users don't have to recreate them (it also avoids supporting 
> different versions of SWIG which I think is non-tenable).
> 
> So in theory (but this doesn't work in reality) its valid to say:
> 
> --disable-swig --enable-ruby --enable-python
> 
> And generate the bindings using the checked-in wrappers.  And in fact, 
> this should be the default
> 
> Obviously that's not very clear.  So what I would prefer is:
> 
> * Keep --enable-ruby and --enable-python
> * Get rid of --enable-swig/-disable-swig
> * Add a new parameter called --regenerate-swig-wrappers
> 
> So the logic is:
> 
> If Python Or Ruby Enabled Then
> 	If regenerate wrappers
>             If detect SWIG
>                regenerate-swig-wrappers = true
>             else
>                regenerate-swig-wrappers = false
>             end
>          end
> 
>          If Python Enabled Then
> 		Check For Python
> 		If Python is found Then
> 			use_python = true
> 		Else
> 			use_python = false
> 		End If
> 	Else
> 		use_python = false
> 	End If
> 
> 	If Ruby Enabled Then
> 		Check For Ruby
> 		If Ruby is found Then
> 			use_ruby = true
> 		Else
> 			use_ruby = false
> 		End If
> 	Else
> 		use_ruby = false
> 	End If
> Else
> 	use_python = false
> 	use_ruby = false
> End If
> 
> Does that make sense?
> 
> Charlie


Hi Charlie,

I think so - however I'm still confused as to why you need the
--regenerate-swig-wrappers option? Can this not be handled as a standard
make target, i.e. regeneration becomes dependent upon the timestamp of
geos.i / geos.i.in?


Kind regards,

Mark.

-- 
ILande - Open Source Consultancy
http://www.ilande.co.uk