Opened 14 years ago
Closed 14 years ago
#2899 closed Bugs (fixed)
Make windows variants compatible with autolink
Reported by: | Vladimir Prus | Owned by: | John Maddock |
---|---|---|---|
Milestone: | Boost 1.39.0 | Component: | None |
Version: | Boost 1.38.0 | Severity: | Problem |
Keywords: | Cc: |
Description
On Windows, Boost.Build builds release shared variant by default. It appears that VC defaults to debug build, so autolink tries to pick mt-gd- binary, which is not found.
What is the best solution here? I am open to any solutions that seems suitable for Windows, and cannot express any position.
John, do you have a comment?
Change History (4)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Thanks. I guess I should ask on the list to see if anybody has objections or better ideas.
comment:4 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I think so, we now build the two variants you've listed by default.
Note:
See TracTickets
for help on using tickets.
Hi Vladimir,
There is no single default that suites everyone here, by default the auto-link headers will be looking for:
link=static runtime-link=dynamic threading=multi debug or release.
So that's two variants, but.... if the user makes any change to their compiler settings (the "code generation options" in the IDE) or wants to link dynamically (with BOOST_*_DYN_LINK) then they'll need different libraries. So I'm strongly of the view that only build-type=complete really delivers what VC++ users need :-(
Oh and then we probably need to support "no-checked-iterators" as a variant as well!
Regards, John.