-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Transmission: Add v4.1.0-beta.3 #6415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
@hgy59, testing with this beta version seems to be okay on my end. Do you have any objection to introducing a beta version to the repo to help resolve issues with certain trackers? |
I do not recommend to publish beta versions for packages that aldready have approved versions. Anyone interested in this beta can download the package created by github build action. |
* Update to 4.0.6 * Use transmission archive that includes the submodules --------- Co-authored-by: hgy59 <[email protected]>
|
@mreid-tt beta.3 is available... This is Transmission 4.1.0-beta.3. We're not in feature freeze yet, so this release includes some new features as well as bugfixes and performance improvements. |
With the latest beta it does not build. From the log, it builds But then the compiler does not look for the same files it built: Not sure if there are any build options to fix this or if this is an upstream issue. |
|
For libcrc32 only the dynamic library is created (libcrc32c.so) but the linker wants to use the static library libcrc32c.a. we don't disable static builds (like define --disable-static) so I don't have a clue what's going wrong... |
|
Hey @mikedld, I recall you assisted with build issues in the past for Transmission on Synology. Looking at the above issue which only appears in the latest beta version, any thoughts on what may be causing it? |
|
Seems like adding IIUC what's causing it is the build scripts setting |
Thanks much for the quick feedback.
@th0ma7, would any of the recent framework changes potentially affect this? |
|
@mreid-tt certainly, I'll try to find some cycles either tomorrow or monday. At first glance I don't see why it would as I don't recall changing stuff specific to cmake, but worth double-checking. Out of curiosity, have you tried building pre vs post framework changes (which I'll do anyway) - the |
|
@mreid-tt just fixed it. We have some code in spksrc.cross-cmake-env.mk that defines and That means, we always add The implementation is a bit shaky, because it adds @th0ma7 only if |
It has nothing to do with latest framework changes. |
You are absolutly right. There is a not so obvious definition of |
|
@hgy59, thanks for looking into this. I guess we'll revisit the need for this fix when Transmission 4.1 is out of beta. |
I'll check that out for certain. Although there are two use cases: with and without toolchain file. I presume what you are referring to is without but still the toolchain file would have something similar defined as well. Absolutely worth a look, and nice catch. |
|
So I've looked through the code and indeed there is something wrong, but only when building in legacy mode i.e. What hapens, is that it checks if Then when generating the "per-dependency" toolchain file which ends-up being located in This check is missing for the legacy CMake build (i.e. no toolchain file) - but this is not impacting your build as you are building normally with using a toolchain file (I feel I repeated toolchain file too often ... 🤷 ). Still, changing the initial test to I'll create a quick PR to patch this. EDIT: @mreid-tt Fix tested using your branch and merged #6784 - you should now be able to safely use |
Description
This pull request includes the following:
Fixes #6410
Checklist
all-supportedcompleted successfullyType of change