On 1/23/06, Branko Čibej <brane@xbc.nu> wrote:
> Ivan Zhakov wrote:
> > On 1/23/06, Branko Čibej <brane@xbc.nu> wrote:
> >
> >>>> Let's follow APR's lead in naming the libraries. APR has
> >>>>
> >>>> apr.lib, aprutil.lib, apriconv.lib -- static libraries
> >>>> libapr.dll/lib libaprutil.dll/lib libapriconv.dll/lib -- DLLs and
> >>>> import libraries.
> >>>>
> >>>>
> >>> I am ok to follow APR naming libraries, but in this case we have one
> >>> problem: now we specify library name already with 'lib' in build.conf,
> >>> so we need strip it for static libraries or change build.conf and add
> >>> 'lib' prefix for dll and *nix libs. What is better?
> >>>
> >>>
> >> No, we don't have to do that. It's enough to teach the Windows generator
> >> to treat those libsvn_foo specially.
> >>
> > It is easy to say "teach the Windows generator" :) Sorry, I am not
> > expert in Windows generator, might be because it is overburden. Could
> > you give me some points how to and where do this?
> >
> Oof, I'd have to dig in myself. And "overburden" is an understatement. :)
>
> I'll try to find time to look into this soon.
Wow, it would be great! I consider that Windows DLLs is important stuff.
So meanwhile I concentrate on other parts of this tasks: factor out
svn_xml_is_xml_name_valid() and teach extractor.py ignore non windows
exports.
If you interesting I can send my current status of generator.
--
Ivan Zhakov
Received on Mon Jan 23 18:21:30 2006