So far, it appears that everything but mod_dav_svn compiles, with the sole
caveat being that almost every lib generates lots of LNK4006 warnings.
Shouldn't be that big a deal, though. Of course, libsvn_swig_java doesn't
compile because I don't have the JDK installed, and libsvn_swig_py doesn't
compile because it's windows (although if you look at issue #990, I have a
diff that will help alleviate that). As far as the rest of the python
bindings, there are no dsp's generated yet for them, so I don't know what
exactly will happen there. Anyways, so far it's looking good.
> -----Original Message-----
> From: Greg Stein [mailto:email@example.com]
> Sent: Friday, April 04, 2003 3:26 PM
> To: Dale Hirt
> Cc: firstname.lastname@example.org
> Subject: Re: [PATCH] subversion/libsvn_subr/libsvn_subr.dsp
> On Fri, Apr 04, 2003 at 02:51:41PM -0800, Dale Hirt wrote:
> > Coolness. I tried it, and it almost works. I got the
> following error when
> > I tried to compile:
> > 'The source files
> "D:\work\subversion\subversion\mod_dav_svn\log.c" and
> > "D:\work\subversion\subversion\libsvn_repos\log.c" are both
> configured to
> > produce the output file
> og.obj". The
> > project cannot be built.'
> How about everything *but* mod_dav_svn? Can you build the
> client? svnadmin?
> And the others?
> We can start nuking .dsp files if that is the case.
> Brandon originally had some code in the .dsp generation to
> deal with those
> conflicting names (there is also a conflict on repos.c). I
> disabled that
> until I better understood the problem. Now I see :-)
> Rather than renaming the files, it might be best to specify
> custom outputs
> for the two that conflict. Note that this only applies to the static
> library. If we generate DLLs for the libraries, then we'll
> have no problem.
> Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Apr 5 02:05:02 2003