Re: [proteowizard-support] tss_workaround.cpp error with 3_0_3900 (2nd attempt to post)

[Damian <df...@um...>]

Thanks Matt.

I finally got it to compile and it now runs as expected.
In case it's of interest to anyone on the list here are the details.

Following your suggestion here is the contents of my quickbuild.sh script:

##--------------------------------------------------------------------------------------------------------
#!/bin/sh

PWIZ_ROOT=$PWD/pwiz_root
PWIZ_BJAM=$PWIZ_ROOT/libraries/boost-build/engine/bin/bjam

BOOST_BUILD_PATH=$PWIZ_ROOT/libraries/boost-build
export BOOST_BUILD_PATH
export PWIZ_ROOT

toolset="gcc"

cmd="$PWIZ_BJAM toolset=$toolset $@"

echo -e "\n$cmd\n"; ## just show the user what the command will be

$cmd

## move the final compiled program to the current directory
GCCVERSION=$(gcc -dumpversion);
mv ./bin/gcc-$GCCVERSION/release/link-static/threading-multi/reader $PWD
##--------------------------------------------------------------------------------------------------------



My Jamroot.jam file for the project is as follows:

exe reader.exe
         : ## source files
                 [ glob ./src/*.cpp ]
         : ## requirements
                 <include>./pwiz_root/pwiz
<library>./pwiz_root/pwiz_tools/common//pwiz_tools_common
<library>./pwiz_root/pwiz/data/msdata//pwiz_data_msdata
<include>./pwiz_root/pwiz/utility/misc//utility_misc
         : ## options
                 <warnings>all
                 <threading>multi
                 <toolset>gcc
                 <link>static
                 <variant>release
                 <optimization>speed
         ;


If anyone is interested in the actual C++ code I wrote I'm happy to 
provide it.

Thanks again for all your help.

Damian


On 08/27/2012 06:32 PM, Matthew Chambers wrote:
> OK, you need to set up BOOST_BUILD_PATH appropriately before calling bjam. That's one of the things
> quickbuild does. Easiest thing is just to make yourself a copy of quickbuild and put it in root. All
> you have to change is the path suffix to the boost-build directory.
>
> Hope this helps,
> -Matt
>
>
> On 8/26/2012 4:48 PM, Damian wrote:
>> Sorry for the confusion.
>> "compiling from the project root" means I run pwiz's version of bjam from /home/dfermin/workspace/pwiz_3
>> Where as "running quickbuild.sh" means I run quickbuild.sh from within /home/dfermin/workspace/pwiz_3/pwiz_root
>>
>> The entire pwiz library is placed inside the pwiz_3/pwiz_root folder and compiled from there with quickbuild.sh
>> To compile my project I wrote a Jamroot.jam file for the project that resides outside the pwiz_root folder
>>
>> Here is the directory structure from pwiz_3 on:
>> pwiz_3/
>> pwiz_3/pwiz_root          ## <-- all of pwiz is in here
>> pwiz_3/Jamroot.jam     ## <-- custom Jamroot file I created to compile my project
>> pwiz_3/src                     ## <-- source code for my project is stored here
>>
>> Hope this helps.
>> Damian
>> On Aug 26, 2012, at 2:54 PM, Matt Chambers wrote:
>>
>>> I'm confused. What is the difference between "compile from the root
>>> directory" and "running quickbuild.sh"? Anyway, this code changed since
>>> 3467 so it's not strange that it broke.
>>>
>>> -Matt
>>>
>>>
>>> On 8/24/2012 8:55 PM, Damian wrote:
>>>> Sorry I spoke to soon with my last post.
>>>> When I compile from the root directory of the project
>>>> (/home/dfermin/pwiz_3) I get this:
>>>> search-path:  ./pwiz_root/libraries/boost-build
>>>> THIS_PATH:
>>>> /home/dfermin/workspace/pwiz_3/pwiz_root/ext/boost/pwiz_root/libraries
>>>>
>>>>
>>>> Although this is strange to me because with the 3.0.3467 this wasn't a
>>>> problem. I inserted the same debugging code you gave me in *that*
>>>> ext-boost.jam file and this is what I got:
>>>>
>>>> search-path:  ./pwiz_root/libraries/boost-build
>>>> THIS_PATH:
>>>> /home/dfermin/workspace/pwiz_3.old/pwiz_root/ext/boost/pwiz_root/libraries
>>>>
>>>>
>>>> Damian
>>>>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> proteowizard-support mailing list
> pro...@li...
> https://lists.sourceforge.net/lists/listinfo/proteowizard-support
>
>

-- 
Damian Fermin, Ph.D
Pathology Dept.
University of Michigan
1300 Catherine St.
Med. Sci. One #4237
Ann Arbor, MI 48109
734-615-0302
df...@um...