Re: [Boost-build] bjam creates libraries names with "vc" instead of "vc80" when compiling for wince

Subject: Re: [Boost-build] bjam creates libraries names with "vc" instead of "vc80" when compiling for wince
From: Krajnak, Mike (GE Healthcare) (michael.krajnak_at_[hidden])
Date: 2011-03-30 13:44:13

I walked through the files one more time to make sure the changes were
saved, I was launching with the right bat script and so on and got the
same result, that is, no vc80, only vc.

If it works for you and not for me that sounds like something else was
tweaked that I've forgotten or didn't know about (mine are about the
third or fourth set of hands involved in editing some of these files).

Some time in April I hope to move to 1.46.  I have a checklist of files
I know I've modified and that I'll be bringing into 1.46, so if it
doesn't work then I'l have a lot more faith that I understand the deltas
between the release and what I have.

Thanks again!

Mike

-----Original Message-----
From: David Deakins [mailto:DDeakins_at_[hidden]] 
Sent: Wednesday, March 30, 2011 12:22 PM
To: Krajnak, Mike (GE Healthcare)
Subject: RE: [Boost-build] bjam creates libraries names with "vc"
instead of "vc80" when compiling for wince

Hmmm... that's odd.  After I posted the message on the list, I was
curious so I went and set up a MSVC toolset in my user-config.jam with a
version label of 'evc9'.  Sure enough I lost the version numbers in my
output library names just like you described (toolset tag was -vc-).
Then I changed it to '9.0~evc' and it went back to showing -vc90- in the
lib files.

The code that generates this part of the library file name is in the
toolset-tag rule of tools\build\v2\tools\common.jam.  It extracts the
version as 

local version = [ MATCH
"<toolset.*version>([0123456789]+)[.]([0123456789]*)"
        : $(properties) ] ;

The regex in that statement makes it look like it does want to see the
X.Y version number there at the beginning of the version string.  But I
can't explain why it didn't seem to resolve your problem...

-Dve

-----Original Message-----
From: Krajnak, Mike (GE Healthcare) [mailto:michael.krajnak_at_[hidden]]
Sent: Wednesday, March 30, 2011 7:00 AM
To: boost-build_at_[hidden]
Subject: Re: [Boost-build] bjam creates libraries names with "vc"
instead of "vc80" when compiling for wince

Thanks for the suggestion, but changing to:

    msvc : 8.0~evc :

 does not seem to have any effect, it builds just as before with just
"vc".

Oddly enough, if I omit the space between "8.0~evc" and the ":" I get an
error:

boost_1_43_0/tools/build/v2/build\toolset.jam:38: in toolset.using
*** argument error
* rule msvc.init ( version ? : command * : options * )
* called with: ( 8.0~evc: D:/Program Files/Microsoft Visual Studio
8/VC/bin/cl.exe : ...

But that's probably not relevant, but as you said, picky.

Thanks again,

Mike

-----Original Message-----
Date: Tue, 29 Mar 2011 11:38:58 -0600
From: David Deakins <ddeakins_at_[hidden]>
To: boost-build_at_[hidden]
Subject: Re: [Boost-build] bjam creates libraries names with "vc"
        instead of "vc80" when compiling for wince
Message-ID: <imt5fj$fn5$1_at_[hidden]>
Content-Type: text/plain; charset=windows-1252; format=flowed

On 3/29/2011 6:27 AM, Krajnak, Mike (GE Healthcare) wrote:
> When I build boost for WinCE using VS2005 I expect the libraries to 
> include ?vc80? in the name, for example
libboost_regex-vc80-mt-sgdp.lib.
>
> But instead of vc80 it just has ?vc?, libboost_regex-vc-mt-sgdp.lib.
>

In your user-config.jam file, I see you have something like this:

using msvc : evc8 :
     "D:/Program Files/Microsoft Visual Studio 8/VC/bin/cl.exe" :
     <compileflags>-D_CRT_SECURE_NO_WARNINGS
     ...

If you change your version parameter to:

using msvc : 8.0~evc :
     "D:/Program Files/Microsoft Visual Studio 8/VC/bin/cl.exe" :
     <compileflags>-D_CRT_SECURE_NO_WARNINGS
     ...

Does that have any effect?  I seem to remember that Boost.Build is picky
about the formatting of that version parameter (but I could be
mis-remembering).

-Dave

DISCLAIMER:
This email and any attachments are confidential, may be attorney-client
privileged and are intended only for the use of the addressee.
Unauthorized use, distribution or copying is forbidden and may be
unlawful. If you have received this email in error, please notify the
sender immediately by return email and delete all copies of this message
and any attachments from your computer.  Thank you.