Hi Bill, For 4.3.x, I moved everything that was still needed from win_lib into trunk/extern. I did this because people often didn't understand that they had to download both directories (tpp and win_lib), and/or that win_lib needed to match the exact version of tpp.
I maintained the Visual Studio VC8 build solely for the purposes of building the SPC converters for the TPP releases: ReAdW, massWolf, trapper, and mzWiff. As these have not significantly changed (from a build point of view) in the last few releases, I'd only been maintaining the "Release" variant of the TPP "solution" on VC8. I did take time to make sure, however, that the release build does indeed uncompress and build everything it needs in TPP/extern (that is, I made sure that a standalone Release build worked, rather than have it depended on having run the mingw build in the same directory, to uncompress everything first.) As it turns out that some TPP developers, such as Brian and yourself, particularly like the VC8 debugger. I can assure you that if you download trans_proteomic_pipeline and qualscore from sashimi/tags/release_4-3-1 in svn as a completely clean download, the Release build will work from start to finish. (It's possible that the build system was confused by build objects/directories from the 4-2 win_lib style layout if you upgraded your source directory, rather than did a clean checkout.) Then, after Release has built, and uncompressed everything in the process, you should be able to switch to the Debug build. However, as you've found, this hasn't been as maintained, and you and/or Brian may need to make a few tweaks to get Debug back up to speed. Moving forward, the SPC converters will be retired in favor of ProteoWizard's msconvert (which is why we hope people are using it now and giving the pwiz team feedback on any issues encountered.) We'll be using the pwiz team's build of the program, so we won't have a direct need to maintain VC8. However devs such as Brian and yourself may end up contributing changes to keep it working, if they prefer the debugger, etc. Hope this info helps. Let us know how it works on your system to try a completely clean checkout of the release_4-3-1 tag followed by a Release build first. -Natalie On Mon, Nov 9, 2009 at 7:27 AM, Bill Nelson <[email protected]> wrote: > > The newer releases don't extract the external libraries. > I was using the XML_only solution. I switched to the plain vanilla TPP > solution, rebuilt ziplib , and everything works now. > I would like to use the trunk but it does not match the documentation: > I can't find the win_lib folder in the trunk. > Can you please guide me to the correct win_lib folder for the trunk or > is it no longer needed? > > Thanks, > Bill > > > On Nov 6, 6:27 pm, Brian Pratt <[email protected]> wrote: >> Just about everything links against tpplib, so yes, if that's not happy >> nobody's happy. And tpplib depends on zlib, so... >> >> I think you're better off looking forward than backward, though, and I'd say >> go with trunk. >> >> >> >> On Fri, Nov 6, 2009 at 2:39 PM, Bill Nelson <[email protected]> wrote: >> >> > I couldn't get 4.3 to work so I went back to 4.2 (because it was the >> > release used in the documentation's build example). >> > It definitely got better and the build was running for about 45 >> > minutes but still no joy. I hope you've seen this one: >> >> > LIB : fatal error LNK1181: cannot open input file 'C:\sashimi >> > \release4-2-1\trans_proteomic_pipeline\src\/Debug/zlib.lib' >> > LINK : fatal error LNK1181: cannot open input file '..\..\..\debug >> > \tpplib.lib' *this one happens in almost every target* >> >> > ========== Build: 7 succeeded, 38 failed, 0 up-to-date, 0 skipped >> > ========== >> >> > On Nov 6, 2:05 pm, Brian Pratt <[email protected]> wrote: >> > > Branch should be fine - trunk build system is being worked on so no >> > surprise >> > > to find a hiccup there. >> >> > > On Fri, Nov 6, 2009 at 10:41 AM, Bill Nelson <[email protected]> >> > wrote: >> >> > > > Hi Brian, >> > > > I am using branch 4-3. do you know the last release that working? >> > > > Thanks for your help. >> > > > Bill >> >> > > > On Nov 6, 1:16 pm, Brian Pratt <[email protected]> wrote: >> > > > > Try a release build first - it handles the uncompressing stuff. >> > > > Apparently >> > > > > just an oversight on the debug side, I'm sure it will get fixed soon, >> > but >> > > > > this should get you rolling. >> >> > > > > On Fri, Nov 6, 2009 at 7:58 AM, Bill Nelson <[email protected]> >> > > > wrote: >> >> > > > > > I'm building tpp on windows with VS8. I checked out 4.3. I have a >> > > > > > couple questions. >> >> > > > > > 1. I wanted to check out the trunk but I could only find win_lib in >> > > > > > the branches; where is win_lib for the trunk? >> > > > > > 2. I assume I need to extract some of the external libs but I >> > can't >> > > > > > find anything in the readme files. In extern I found: >> > > > > > bjam_src.tgz >> > > > > > boost_1_39_0.tar.bz2 >> > > > > > expat-2.0.1.tar.gz >> > > > > > libarchive-2.2.7.tar.gz >> > > > > > sqlite-amalgamation-3.6.15.tar.gz >> > > > > > Which ones do I need and where do they go? >> >> > > > > > It looks like the build script tried to extract them but I can't >> > find >> > > > > > any boost stuff other than the archive and there are a lot can't >> > find >> > > > > > boost errors in the build: >> >> > > > > > 1>zlib - 0 error(s), 14 warning(s) >> > > > > > 3>------ Build started: Project: boost_vc8, Configuration: Debug >> > Win32 >> > > > > > ------ >> > > > > > 4>------ Build started: Project: regenerate_versionInfo, >> > > > > > Configuration: Debug Win32 ------ >> > > > > > 3>Performing Makefile project actions >> > > > > > 3>Setting environment for using Microsoft Visual Studio 2005 x86 >> > > > > > tools. >> > > > > > 3>Archive: bjam.zip >> > > > > > 3> inflating: bjam.exe >> > > > > > 3>The system cannot find the path specified. >> > > > > > 3>"extracting boost source code; this may take a few minutes..." >> > > > > > 3>"done extracting boost source code" >> > > > > > 3>ECHO is off. >> > > > > > 3>The system cannot find the path specified. >> > > > > > 3>"buildling boost libraries; this may take some time..." >> > > > > > 3>The system cannot find the path specified. >> > > > > > 3>"done building boost libraries" >> > > > > > 3>ECHO is off. >> > > > > > 3>The system cannot find the path specified. >> > > > > > 3>Build log was saved at "file://c:\sashimi\win_lib\Debug >> > > > > > \BuildLog.htm" >> > > > > > 3>boost_vc8 - 0 error(s), 0 warning(s) >> >> > > > > > The build log did not have much to say. >> >> > > > > > Thanks, >> > > > > > Bill > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "spctools-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/spctools-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
