[DiscordArchive] Isn't boost kind of a "staging area" for std:: code prototypes (or sth)? How about if the functional
[DiscordArchive] Isn't boost kind of a "staging area" for std:: code prototypes (or sth)? How about if the functional
Original source
Isn't boost kind of a "staging area" for std:: code prototypes (or sth)? How about if the functionality gets moved to std:: ?
rektbyfaith
04-23-2024, 10:27 AM #1Archived author: chipzz • Posted: 2024-04-23T10:27:05.410000+00:00
Original source
Isn't boost kind of a "staging area" for std:: code prototypes (or sth)? How about if the functionality gets moved to std:: ?
Original source
I would say: stick with the versions recommended in the guide. There is a common (and very very very false IMO) misconception that newer somehow necessarily equals better, which is very often not the case.
Leave experimenting with newer boost versions to the people who understand the code base enough to actually fix things
rektbyfaith
04-23-2024, 10:30 AM #2Archived author: chipzz • Posted: 2024-04-23T10:30:55.069000+00:00
Original source
I would say: stick with the versions recommended in the guide. There is a common (and very very very false IMO) misconception that newer somehow necessarily equals better, which is very often not the case.
Leave experimenting with newer boost versions to the people who understand the code base enough to actually fix things
Original source
Also <@200677690838220800> , this is a perfect example of where vcpkg would have prevented this problem, by means of pinning a baseline. So, vcpkg when?
rektbyfaith
04-23-2024, 10:37 AM #3Archived author: chipzz • Posted: 2024-04-23T10:37:28.415000+00:00
Original source
Also <@200677690838220800> , this is a perfect example of where vcpkg would have prevented this problem, by means of pinning a baseline. So, vcpkg when?
Original source
last time i checked vcpkg had a broken boost port thanks to xz backdoor
rektbyfaith
04-23-2024, 10:39 AM #4Archived author: Tea • Posted: 2024-04-23T10:39:01.929000+00:00
Original source
last time i checked vcpkg had a broken boost port thanks to xz backdoor
Original source
Which would not have been an issue if you pinned the baseline to a commit earlier than the xz problem
rektbyfaith
04-23-2024, 10:39 AM #5Archived author: chipzz • Posted: 2024-04-23T10:39:38.284000+00:00
Original source
Which would not have been an issue if you pinned the baseline to a commit earlier than the xz problem
Original source
no, its because xz repository was taken down so you cant even access old versions
rektbyfaith
04-23-2024, 10:40 AM #6Archived author: Tea • Posted: 2024-04-23T10:40:08.538000+00:00
Original source
no, its because xz repository was taken down so you cant even access old versions
Original source
but do the boost components TC uses depend, even indirectly, on xz?
rektbyfaith
04-23-2024, 10:40 AM #7Archived author: chipzz • Posted: 2024-04-23T10:40:39.337000+00:00
Original source
but do the boost components TC uses depend, even indirectly, on xz?
Original source
oh, its back up now
rektbyfaith
04-23-2024, 10:42 AM #8Archived author: Tea • Posted: 2024-04-23T10:42:16.190000+00:00
Original source
oh, its back up now
Original source
Anyway, I would like to make some progress on the vcpkg front. Doesn't need to be an all-in right away, but there's things that can be done
rektbyfaith
04-23-2024, 10:44 AM #9Archived author: chipzz • Posted: 2024-04-23T10:44:50.301000+00:00
Original source
Anyway, I would like to make some progress on the vcpkg front. Doesn't need to be an all-in right away, but there's things that can be done
Original source
For example your branch has some CMake fixes, maybe these could be applied independently from the rest of your patch?
rektbyfaith
04-23-2024, 10:45 AM #10Archived author: chipzz • Posted: 2024-04-23T10:45:20.998000+00:00
Original source
For example your branch has some CMake fixes, maybe these could be applied independently from the rest of your patch?
1 Guest(s)
1 Guest(s)