Stefan Küng wrote:
> Arne Moor wrote:
>
>> I'm trying to build TSVN from source. Initialy I started with the RC1
>> sources and followed the steps in build.txt
>> ....
>> BTW: Can the theasaurus files also be downloaded?
>
>
> Yes, but make sure you take the ones for OO2, not OO1.x!
>
On the URL http://lingucomponent.openoffice.org/ you won't find the
English thesaurus, there only (some) of the dics can be found. You need
to go (manually) to
http://ftp.services.openoffice.org/pub/OpenOffice.org/contrib/dictionaries/
to find them, they are masked as thes_xx_YY_v2.zip
Question: Where do these files need to be placed? Same place as the .aff
and .dic files?
>> - Downloaded the tools.zip
>> (Is it a good idea from copyright view to include hhc.exe?)
>
> If MS complains, we'll remove it.
Your decision. Since a lot of things already needed to be downloaded I
would remove them and point to MS...
>> - SubWCrev.exe complained about required a DLL at startup....
>> Researched this and found that I need to add:
>> <variable name="PATH"
>> value="E:\DEV\SVN\TortoiseSVN\ext\apr\Release\;%PATH%" />
>> <variable name="PATH"
>> value="E:\DEV\SVN\TortoiseSVN\ext\apr-util\Release\;%PATH%" />
>> <variable name="PATH"
>> value="E:\DEV\SVN\TortoiseSVN\ext\apr-iconv\Release\;%PATH%" />
>> <variable name="PATH"
>> value="D:\SVN\TortoiseSVN\ext\svn-win32-libintl\bin\;%PATH%" />
>
>
> I think that last step isn't really needed. Ok, I admit the build script
> seems broken. But if you build it a second time, SubWCRev will find
> those dll's because they get copied there after the build.
Tried a second "nant setup", still the same error. A Msgbox is popping
up complaining about libapr.dll. Afterwards the buildscript stops.... :-(
>
>> - Build went through. I recognized that there are errors in the
>> building.log and
>
> > that the msi had a different size that rc1-msi from the website.
>
> You will actually see always a lot of errors.
> Reasons:
> - we build Subversion twice (all libs), but once without network/BDB
> support. In that build, you'll get linker errors a lot - but we only use
> those libs from that build which build successfully.
Yes, I read this already in the archive, but was still thinking of it,
because the errors are others then stated in the build.txt. Maybe a
changed note about ne_xxxxx would avoid this too.
> - while generating the docs, there are also a lot of 'errors', but you
> can ignore those - the pdf will get built anyway.
I guessed that, because they didn't look that serious. Thanks for
confirmation.
>
> The different filesize of the msi is completely expected:
> We build TSVN with debug information. And that debug information also
> contains the full paths to the sourcefiles. So if you don't have the
> *exact* same paths as I do, you'll get slightly different filesizes.
OK. Wasn't thinking about a debug build, instead of a release build. But
then it makes absolute sense! Also worth a note :-)
>
>> - Switched to
>> http://tortoisesvn.tigris.org/svn/tortoisesvn/branches/1.3.x Revision
>> 5346
>> - Moved the sources to the VM, restarted the build process.
>> - Got an exception in hhc.exe together with the question from VS.net
>> if I want to debug hhc.exe...
>
>
> I sometimes get that one too. If you get it all the time, you must
> install language support for eastern languages (you might need to insert
> the XP installation CD, so have it ready).
>
Will try that if it continues to happen.
>> - Made a copy of the building.log and answered afterwards with "no",
>> the build was continuing.
>> Result:
>> Nightly build 5346 -> 7'206'912 bytes
>> My build 5346 -> 7'203'840 bytes
>
>
> That difference is due to different paths where our sources live - see
> my comments above.
>
Yep.
>> My Questions:
>> 1. Is it normal that the DLL's are missing? Do those of you who are
>> able to build just have those DLL's in any version (by mistake?) in
>> the windows path?
>> 2. Does anybody know why hhc.exe crashs?
>
>
> hhc crashes quite often. I learned to live with it :)
>
Hopefully I will learn to live with that too...
>> 3. Why get I twice 104 errors in the log while the libsvn_ra_dav-1.lib
>> was linked, all of them started with "error LNK2019: unresolved
>> external symbol _ne_........" or with "error LNK2001: unresolved
>> external symbol _ne_"
>> Directly after the second linking I saw "[exec] 'svn' failed to
>> start." in the log
>> 4. There are a lot of other errors, most likely releated to the
>> documentations. Are those also normal?
>
>
> See my comments above about this.
>
> Stefan
>
Arne
BTW: You search a job in ZH? I just saw a request for a subversion
specialist in our intranet... Nope this is more a joke than a real
question, but I had to laugh this morning about that offer.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jan 5 23:39:12 2006