Thank you, Dmitrii; again, I had misunderstood at my first reading-- thanks for clarifying. Maybe we can come up with a parameter to pass from the boost build vsproj into the .bat script to help identify the MSVC toolchain.
-Natalie On Tue, Apr 14, 2009 at 12:44 PM, Dmitrii Tchekhovskoi <dmitrii...@gmail.com > wrote: > > Hi Natalie, > > I would like to note that (4) is *necessary* for building TPP with MSVS > 2005 SP1 *if* MSVS 2008 has been installed under the same Windows. > > Regards > > Dmitrii > > > Natalie Tasman wrote: > > Hi Dmitri, > > > > I may have misunderstood you in 2) above: you do want to download > qualscore, > > trans_proteomic_pipeline, and win_lib (either from trunk or whatever > branch > > you're working in)-- the other directories are not needed, as you > suggested. > > > > -Natalie > > > > > > On Mon, Apr 13, 2009 at 1:40 PM, Natalie Tasman > > <ntas...@systemsbiology.org>wrote: > > > > > >> Hi Dmitri, > >> > >> Thanks for sharing your notes. Hopefully you found some of the text in > the > >> README_WIN.txt file at the top level helpful as well. > >> > >> Reponding to your points: > >> > >> 2) qualscore is not used by the TPP build process, but is required by > the > >> TPP installer build process. Win_lib *is* extensively used by the > windows > >> build version. > >> > >> 3) removing svn files will save disk space, but make it quite difficult > for > >> you to update your local copy of the sourcecode. You didn't mention > which > >> branch you're using, but trunk (the main development branch) is not > >> guaranteed to be stable and changes quite often; thus it is likely you'd > >> want to be able to update your local source. (From later comments, you > are > >> indeed using trunk.) > >> > >> 4) The TPP is currently only tested with Visual Studio 2005. Thanks for > >> sharing this note for VS 2008. > >> > >> Regarding the other points, you're finding what it's like on the > "bleeding > >> edge". We rarely recommend that people use trunk for developing the > TPP. > >> The stable branch, currently branches/4-2, is the recommended place to > >> start. Again, trunk is not guaranteed to work, especially on all build > >> systems. Many of your issues are changes that were developed on linux > and > >> had not yet been resolved for VS 2005. > >> > >> Thanks again for sharing your experiences. Please let us know if you'd > >> like to submit any code/build changes for inclusion in SVN. Best > wishes, > >> > >> Natalie > >> > >> > >> On Mon, Apr 13, 2009 at 12:49 PM, Dmitrii Tchekhovskoi < > >> dmitrii...@gmail.com> wrote: > >> > >> > >>> Hi, > >>> > >>> I tried to rebuild the developer's version of TPP freshly downloaded > >>> from Sashimi SVN on 04/13/2009. To build the Debug version I used MSVS > >>> 2005 Pro SP1 under Win XP SP3, 32-bit. I would like to share my > >>> experience so that others may avoid stepping on the same rake or > >>> appropriate changes be made to the Sashimi SVN files. How to use > >>> TortoiseSVN or another SVN client is out of the scope of this exercise. > >>> > >>> (1) Download the "trunk" of the TPP from Sashimi SVN > >>> > >>> (2) Copy folders qualscore, trans_proteomic_pipeline, and win_lib into > a > >>> separate folder, in this example c:\tpp. > >>> If I am not mistaken, the contents of other folders are not needed. > >>> > >>> (3) [optionally] Remove unneeded svn files by running the following > >>> command from the command prompt in c:\tpp folder: > >>> for /r %a in (.svn) do rd /S /Q "%a" > >>> > >>> (4) If you have MSVS 2008 also installed on your PC then you need to > >>> modify the file > >>> c:\tpp\win_lib\build_boost_vc8.bat > >>> Locate in this file the line (#13) that begins with > >>> ..\bjam --toolset=msvc "-sNO_ZLIB=0" <...> > >>> and add -8.0 to msvc: > >>> ..\bjam --toolset=msvc-8.0 "-sNO_ZLIB=0" <...> > >>> otherwise boost will not be build successfully: bjam would be trying to > >>> use msvc 9.0 (MSVC 2008) pre-built libraries which are not provided. > >>> > >>> Interestingly, this bug has been sitting there for quite a while. > >>> > >>> (5) Manually expand > >>> c:\tpp\trans_proteomic_pipeline\extern\expat-2.0.1.tar.gz > >>> preserving folder structure inside it to > >>> c:\tpp\trans_proteomic_pipeline\extern\ > >>> This would create folder > >>> c:\tpp\trans_proteomic_pipeline\extern\expat-2.0.1 > >>> > >>> (6) MSVC libraries don't have strsep() string function although it is > >>> used in MzXML2Search.cxx. > >>> Locate in the source file > >>> > c:\tpp\trans_proteomic_pipeline\src\Parsers\MzXML2Search\MzXML2Search.cxx > >>> function > >>> void convert(char *szXMLFile, const OptionsStruct& options) > >>> and insert before it an implementation of strsep from, for example, > from > >>> http://www.winehq.org/pipermail/wine-patches/2001-November/001322.html > >>> I would suggest to surround strsep() body with conditional compilation > >>> instructions: > >>> #if( _MSC_VER == 1400 ) > >>> // MS VC 2005 only > >>> <strsep code> > >>> #endif > >>> > >>> (7) Open c:\tpp\trans_proteomic_pipeline\src\TPP.sln in MSVS 2005 SP1. > >>> > >>> (8) Add the existing file > >>> > >>> > c:\tpp\trans_proteomic_pipeline\src\Search\SpectraST\SpectraSTTsvLibImporter.cpp > >>> to the Source Files folder of the "tpplib" project > >>> > >>> (9) Rebuild the whole solution > >>> > >>> Note: project msvc_makeinstall will be skipped according to the TPP > >>> solution settings > >>> > >>> Switching the Solution Configuration to "Release Static" and rebuilding > >>> was also completed without compile/build errors except for > >>> msvc_makeinstall. > >>> The first error was easy to fix: instead of producing batchcoverage.exe > >>> I had to make the linker produce BatchCoverage.exe (the difference is > in > >>> letter case only?!) > >>> The second error I did not fix and gave up: the MSVC solution did not > >>> create pep_dbcount.exe required by msvc_makeinstall. > >>> This file seems to be created only by > >>> c:\tpp\trans_proteomic_pipeline\src\Makefile > >>> or > >>> c:\tpp\trans_proteomic_pipeline\src\util\Makefile > >>> > >>> The question if the executables built in this exercise work properly or > >>> not is out of the scope of this exercise. > >>> > >>> Several other changes may be needed to compile successfully: since I > >>> merged my old fixed code with the new from Sashimi SVN I could have > >>> missed them due to the smart updating done by TortoiseSVN. > >>> > >>> Regards > >>> > >>> Dmitrii > >>> > >>> > >>> > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "spctools-discuss" group. To post to this group, send email to spctools-discuss@googlegroups.com To unsubscribe from this group, send email to spctools-discuss+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/spctools-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
