Russell Yanofsky wrote:
> Max Bowsher wrote:
>> Yes. I agree with all you say above. My point is that future versions
>> of swig will *NOT* install a swig runtime library. Instead, swig
>> users will be expected to run a swig command generating a .c file
>> which they compile and link into a library of their own, which
>> provides the swig runtime features.
>
> Really? I know that they added a command to generate a .c file containing
> the runtime, but I didn't know they were going to get rid of the automatic
> build and install
>
>> In our case, it seems to make the
>> most sense to integrate this into the existing libsvn_swig_py.
>
> If we do have to start generating swig runtimes on unix (like we already do
> on windows), I think we should leave them as seperate libraries instead of
> combining them into the binding utility libraries. The two sets of libraries
> do different things and come from separate sources.
Depends how you think of it.
I think of them both doing the same thing: "being common support code for the individual bindings libraries"
and coming from the same source: "the subversion build process".
Can you elaborate on why you don't like the idea of combining them? Thanks.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 8 16:51:24 2004