[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: r10039 - in trunk: . build/generator subversion/bindings/swig subversion/bindings/swig/perl/libsvn_swig_perl subversion/bindings/swig/perl/native

From: Ben Reser <ben_at_reser.org>
Date: 2004-06-27 23:19:26 CEST

On Sat, Jun 26, 2004 at 01:44:36PM -0400, Russell Yanofsky wrote:
> * Stop picking up compiler options from `perl -MExtUtils::Embed -e ccopts`
> On ActiveState Perl this returns options like -DPERL_IMPLICIT_SYS which
> don't work with the subversion bindings on Windows.

This means your perl is misconfigured. ccopts just prints runs:
perl_inc(), ccflags() and ccdlflags()

perl_inc() prints:
-I$Config{archlibexp}/CORE

ccflags prints:
$Config{cclfags}

and

ccdlflags prints:
$Config{ccdlflags}

The Config values are probably set for the build environment used to
build the version of Perl you have installed. If you didn't build it
yourself and it was built with a different toolchain, it very likely
won't be right. This means you need to fix it.

> * Specify different library paths because libraries have different names and
> locations on windows

See below...

> * Invoke 'nmake' instead of 'make' internally

Yup we should be using $(MAKE) not make in the Makefile.

> - LIBS => [join(' ', $apr_ldflags,
> - (map {$_ = abs_path($_); "-L$_"} @ldpaths),
> - @ldmodules, '-lsvn_swig_perl-1',
> - `$swig -perl -ldflags`)],
> + LIBS => [join(' ', ('M:/russ/source/svn/Release/subversion/bindings/swig/perl/swigpl.lib',
> + 'M:/russ/source/svn/Release/subversion/bindings/swig/perl/libsvn_swig_perl/libsvn_swig_perl-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_client/libsvn_client-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_delta/libsvn_delta-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_diff/libsvn_diff-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_fs/libsvn_fs-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_fs_base/libsvn_fs_base-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_fs_fs/libsvn_fs_fs-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_ra/libsvn_ra-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_ra_dav/libsvn_ra_dav-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_ra_local/libsvn_ra_local-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_ra_svn/libsvn_ra_svn-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_repos/libsvn_repos-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_subr/libsvn_subr-1.lib',
> + 'M:/russ/source/svn/Release/subversion/libsvn_wc/libsvn_wc-1.lib',
> + 'M:/russ/source/httpd-2.0.49/srclib/apr/Release/libapr.lib',
> + 'M:/russ/source/httpd-2.0.49/srclib/apr-iconv/Release/libapriconv.lib',
> + 'M:/russ/source/httpd-2.0.49/srclib/apr-util/Release/libaprutil.lib',
> + 'M:/russ/source/httpd-2.0.49/srclib/apr-util/xml/expat/lib/LibR/xml.lib',
> + '"K:/Program Files/Microsoft SDK/Lib/ShFolder.Lib"',
> + 'M:/russ/source/svn/neon/libneon.lib',
> + 'M:/russ/source/db4-win32/lib/libdb42.lib'))],

Yikes, some of these are outside our source tree. Also doens't the MS
linker use -L and -l? Shouldn't some of these e.g. K:/Program
Files/Microsoft SDK/Lib/SHFolder.Lib be on the standard search path?
From the looks of it, it seems to me that you're statically linking
everything in. Is this the case?

I guess I don't see a good way of detecting at build time all of that.

-- 
Ben Reser <ben@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 27 23:20:12 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.