Opened 15 years ago
Last modified 13 years ago
#957 new Bugs
The "Getting Started" page does not mention the stdlib option
| Reported by: | Vincent Torri | Owned by: | Thomas Witt |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | Getting Started Guide |
| Version: | Boost 1.34.0 | Severity: | Problem |
| Keywords: | Cc: |
Description
The "Getting Started" page does not mention the stdlib option, that allows to compile using STLport for example.
Also, maybe it is also worth mentionning that using STLport when compiling Boost leads to linking error when the box is linux (and maybe other unix OS). See http://lists.boost.org/boost-users/2007/04/26818.php
Change History (6)
comment:1 by , 15 years ago
| Milestone: | → Boost 1.34.1 |
|---|---|
| Owner: | set to |
| Severity: | → Showstopper |
comment:2 by , 15 years ago
| Owner: | changed from to |
|---|
comment:3 by , 15 years ago
| Milestone: | Boost 1.34.1 → Boost 1.35.0 |
|---|
Moved to 1.35.0 as it's controversial. I am sympathetic with Dave's opinion.
comment:4 by , 15 years ago
I'm trying to clean up the documentation related tickets. Is it okay if I resolve this as 'wontfix'?
comment:5 by , 15 years ago
No, I'd prefer to have a chance to see if there's a good way to fit the option in before I make that determination.
comment:6 by , 13 years ago
| Component: | None → Getting Started Guide |
|---|---|
| Milestone: | Boost 1.36.0 → To Be Determined |
| Severity: | Showstopper → Problem |
Note:
See TracTickets
for help on using tickets.
IMO using an alternate standard library is out-of-scope of what I intended for the getting started guide. My feeling was that stuff like that belonged in the BBv2 docs. If the getting started guide is going to become a "build whatever weird-arsed configuration you may need" guide, I want that to be an explicit decision. So let's discuss it.