Re: [PATCH] Generating VC6 project files for swig bindings

Russell Yanofsky wrote:

>>Now I'd like to see a few things changed, if you don't mind. :-)
>>
>>
>
>Ok. I was able to handle these things:
>
>
>
>> * Move the unique() function to gen_base.py. There are quite a few
>> places where we can use it.
>> * Prefix the project names with "swig_"; e.g., "swig_python_core"
>> instead of just "python_core". This will make the project lists
>> more readable.
>> * Add new pseudo projects (in build.conf): __SWIG_PYTHON__ and
>> __SWIG_JAVA__, to build all the relevant bindings in one fell
>> swoop. * Put the target description back in, so that we get
>> version info in the generated DLLs.
>>
Great!

>But not these:
>
>
>> * Change the SWIG custom build commands to generate the C files in
>> the build tree (Release or Debug), _not_ the source tree. This
>> means tweaking the source file definitions for the C files, too.
>>
Oh well, I guess we can live with that.

>> * Fix the link warnings about not finding aprutil_src.pdb or
>> xml_src.pdb -- I guess that means adding library dependencies to
>> the link lines for the DLLs.
>>
>>
>
>I couldn't figure out a way to tell Visual C++ to compile different C source
>files depending on the configuration (release or debug). I tried putting
>conditionals ('!IF "$(CFG)" == "whatever" / !ENDIF) around the SOURCE=...
>statements in the project files, but that made only them unloadable. So swig
>still outputs the C files in the source tree since it's a neutral location.
>
>I couldn't do anything about the link warnings since I don't get them and I
>don't know what causes them.
>
Hm, maybe I did something stupid the last time I built apr-util.

Thanks for the patch. I'll review and/or install, as appropriate.

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org