Sam Watkins wrote:
> hi, I downloaded VS2008 (trial) and have been trying to compile
> tortoise-svn with it. I encountered these issues and fixed them:
The 1.4.x branch and releases can't be compiled without hacking with
VS2008, but you can build the trunk with it just fine. In fact, the
trunk now builds better with VS2008 than with VS2005 since that's what
I'm using now.
> build failed in neon, removed:
> #define snprintf _snprintf
> #define vsnprintf _Vsnprintf
Known issue. neon < 0.28 has that problem. But I sent a patch to Joe
Orton, and neon 0.28 has this fixed now.
> removed "clean" from openssl "OpenSSL" target deps.
Why?
> upgraded ".sln" file in visual studio
>
> edited C:\SVN\TortoiseSVN\src\TortoiseSVNSetup\StructureFragment.wxs,
> change vc80 to vc90 and VC80 to VC90, also 8_0 to 9_0.
>
> GDIPLUS.MSM is missing (merge module). I got it from installshield.com
> (this should be mentioned in build.txt again?)
it's mentioned in build.txt on trunk.
> Everything builds now except the setup program, there is still a problem
> so I'm asking for help, when compiling I get:
>
> setup:
>
> [script] Scanning assembly "qemomqjj" for extensions.
> [exec] TortoiseSVN.wxs
> [exec] FeaturesFragment.wxs
> [exec] StructureFragment.wxs
> [exec] UIFragment.wxs
> [exec] light.exe : error LGHT0001 : Error HRESULT
> E_FAIL has been returned from a call to a COM
> component.
> [exec]
> [exec] Exception Type:
> System.Runtime.InteropServices.COMException
> [exec]
> [exec] Stack Trace:
> [exec] at
> Microsoft.Tools.WindowsInstallerXml.IMsmMerge2.Merge(String
> feature, String directory)
> [exec] at
> Microsoft.Tools.WindowsInstallerXml.Binder.MergeModules(String
> databasePath, Output output)
> [exec] at
> Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output
> output)
> [exec] at
> Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[]
> args)
>
> BUILD FAILED
>
> C:\SVN\TortoiseSVN\src\TortoiseSVNSetup\setup.build(86,6):
> External Program Failed: light (return code was 1)
>
>
> Maybe this is something to do with GDIPLUS, as far as I can see
> GDIPLUS.DLL is not used any more but GDI32.DLL is used instead. Anyway
> please let me know if you can help. Thanks!
If you haven't changed the wxs files apart from what you've mentioned,
it should work (and use the merge module of gdiplus, not the dll).
Are you using WiX v2? Because WiX v3 doesn't work (but I think you would
get different errors).
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-02-16 09:04:00 CET