viewer.git/indra/linux_crash_logger/CMakeLists.txt, branch 26.3Megapahit's fork of the Second Life viewer.
https://megapahit.org/viewer.git/atom?h=26.32022-04-30T22:38:40ZRemove setting of HEADER_FILE_ONLY on .h* files, cmake automatically2022-04-30T22:38:40ZNickynicky.dasmijn@gmail.com2022-04-30T22:38:40Zurn:sha1:283c2a20cc4ef856076d287303c7143332b201fe
sets the property on those.
create target ll::uilibraries to have one common target that defines what each2022-04-16T15:28:26ZNickynicky.dasmijn@gmail.com2022-04-16T15:28:26Zurn:sha1:924fa0fa78b41c7e8486c1ed29764afb1e32fd7e
operation system needs as dependencies on OS gui libraries.
Rework cmake, the original plan was to maybe be able to use conan targets with the same name (that's why 3ps had names like apr::apr),2022-04-13T17:21:55ZNickynicky.dasmijn@gmail.com2022-04-13T17:21:55Zurn:sha1:241919e7f7986c11586a49bff53cf19c2c0e0ea6
but it's safer and saner to put the LL 3ps under the ll:: prefix.
This also allows means it is possible to get rid of that bad "if( TRAGET ...) return() endif()" pattern and rather use include_guard().
This set of changes reverts the merge with master (git revert c83e740) and results in a version of the DRTVWR-519 that matches what was presemt before it was deployed as a release viewer *plus* 3 small fixes from Maxim (See commits). This branch can now be used for additional fixes before eventually being used to release D-519 as normal2021-03-09T22:39:51ZCallum Prenticecallum@lindenlab.com2021-03-09T22:39:51Zurn:sha1:168d177197bd7558bbe0ca13d01c984ad8638da7Revert "Merge branch 'master' of https://bitbucket.org/lindenlab/viewer into DRTVWR-519"2021-03-08T13:56:16ZBrad Payne (Vir Linden)vir@lindenlab.com2021-03-08T13:56:16Zurn:sha1:c83e740ef94e16ba85574454f3138905edecb029
This reverts commit e61f485a04dc8c8ac6bcf6a24848359092884d14, reversing
changes made to 00c47d079f7e958e473ed4083a7f7691fa02dcd5.
Some small changes to replace 'vfs' with 'filesystem' outside of my dev env2020-09-17T18:28:37ZCallum Prenticecallum@gmail.com2020-09-17T18:28:37Zurn:sha1:d9d1b12f5f3d6f8cbb0780ef8c0aa7844972bbe2SL-793: Use Boost.Fiber instead of the "dcoroutine" library.2020-03-25T21:32:45ZNat Goodspeednat@lindenlab.com2018-05-11T01:46:07Zurn:sha1:66981fab0b3c8dcc3a031d50710a2b24ec6b0603
Longtime fans will remember that the "dcoroutine" library is a Google Summer
of Code project by Giovanni P. Deretta. He originally called it
"Boost.Coroutine," and we originally added it to our 3p-boost autobuild
package as such. But when the official Boost.Coroutine library came along
(with a very different API), and we still needed the API of the GSoC project,
we renamed the unofficial one "dcoroutine" to allow coexistence.
The "dcoroutine" library had an internal low-level API more or less analogous
to Boost.Context. We later introduced an implementation of that internal API
based on Boost.Context, a step towards eliminating the GSoC code in favor of
official, supported Boost code.
However, recent versions of Boost.Context no longer support the API on which
we built the shim for "dcoroutine." We started down the path of reimplementing
that shim using the current Boost.Context API -- then realized that it's time
to bite the bullet and replace the "dcoroutine" API with the Boost.Fiber API,
which we've been itching to do for literally years now.
Naturally, most of the heavy lifting is in llcoros.{h,cpp} and
lleventcoro.{h,cpp} -- which is good: the LLCoros layer abstracts away most of
the differences between "dcoroutine" and Boost.Fiber.
The one feature Boost.Fiber does not provide is the ability to forcibly
terminate some other fiber. Accordingly, disable LLCoros::kill() and
LLCoprocedureManager::shutdown(). The only known shutdown() call was in
LLCoprocedurePool's destructor.
We also took the opportunity to remove postAndSuspend2() and its associated
machinery: FutureListener2, LLErrorEvent, errorException(), errorLog(),
LLCoroEventPumps. All that dual-LLEventPump stuff was introduced at a time
when the Responder pattern was king, and we assumed we'd want to listen on one
LLEventPump with the success handler and on another with the error handler. We
have never actually used that in practice. Remove associated tests, of course.
There is one other semantic difference that necessitates patching a number of
tests: with "dcoroutine," fulfilling a future IMMEDIATELY resumes the waiting
coroutine. With Boost.Fiber, fulfilling a future merely marks the fiber as
ready to resume next time the scheduler gets around to it. To observe the test
side effects, we've inserted a number of llcoro::suspend() calls -- also in
the main loop.
For a long time we retained a single unit test exercising the raw "dcoroutine"
API. Remove that.
Eliminate llcoro_get_id.{h,cpp}, which provided llcoro::get_id(), which was a
hack to emulate fiber-local variables. Since Boost.Fiber has an actual API for
that, remove the hack.
In fact, use (new alias) LLCoros::local_ptr for LLSingleton's dependency
tracking in place of llcoro::get_id().
In CMake land, replace BOOST_COROUTINE_LIBRARY with BOOST_FIBER_LIBRARY. We
don't actually use the Boost.Coroutine for anything (though there exist
plausible use cases).
remove only-partially-successful attempt to put teamcity blocks around targets2018-09-07T13:13:57ZOz Lindenoz@lindenlab.com2018-09-07T13:13:57Zurn:sha1:9fd463bd9496ba5d97abec6ee75b9c0c089aa69dadd more block structure to TeamCity log output for components2018-09-05T22:07:35ZOz Lindenoz@lindenlab.com2018-09-05T22:07:35Zurn:sha1:49c483eeb350f3620f26ce933007c3d4e9f66d4fmerge with 4.0.3-release2016-04-04T19:53:09ZOz Lindenoz@lindenlab.com2016-04-04T19:53:09Zurn:sha1:9be58e915a6c69de280ccabd3019e9ac40beed26