Vsomeip support on kirkstone #yocto #kirkstone - yocto

I am trying vsomeip on the latest yocto/poky branch kirkstone. I modified the yocto recipe to some extent. Hardcoded Vsomeip to be 3.1.20.1 with no patches and chose BOOST 1.74 after lot of experiments and errors. But still compilation fails. I get a string of errors like:
/basic_socket_ext_local.hpp:133:7: error: no matching function for call to 'boost::asio::detail::io_object_impl<boost::asio::detail::reactive_socket_service_ext_local<boost::asio::local::stream_protocol_ext>, boost::asio::executor>::io_object_impl(boost::asio::io_context&)'
Can anyone tell me the right BOOST version that is compatible with VSOMEIP version? or any patch for 3.1.20 (the patch that came 0001-Support-boost-v1.66.patch didnt work either) Any repo with vsomeip on kirkstone available?

Related

What does "version" at the end of a Swift Package Manager Package.resolved file mean?

I am trying to figure out what "version": 1 or "version": 2 at the end of a Package.resolved file generated by Swift Package Manager stands for. I have two workspaces and sometimes the Package.resolved files have both version 1 or 2, sometimes different versions.
What kind of impact has having different versions and what is causing the version change? Is it possible to have the same versions for both?
I've done a bit of research and it seems Apple changed the format of the Package.resolved file with version 5.6 of the Swift tools. Any version of the toolchain can work with version 1 but you need >= 5.6 to work with version 2. See this forum conversation
https://forums.swift.org/t/using-swiftpm-5-6-and-supporting-older-versions/55708/9
As I said in my comment, it's probably best to ignore what's in that file and not commit it to your source code control. One of the comments in the above forum thread mentions that you might want to commit it to ensure repeatability of builds, but that is a fragile solution and if you want to build with exact versions, you should do this in the Package.swift file.
Addendum
You'll get mixed versions because, if resolving a package means no changes, spm will not overwrite the old Package.resolved.

Having and error with dart2js as a result of dash_chat

dart2js error with dash_chat
One of our existing applications makes use of dash_chat, which is working on a V2, however, v2 has a fraction of the APIs implemented. The project is somewhat dormant so today we just doing housekeeping and trying to keep the project up-to-date.
I am now getting this error, and sadly I went and updated all packages and we are using FLutter 3 and Dart 2.17 in all our other projects.
Target dart2js failed: Exception: Warning: The 'dart2js' entrypoint script is deprecated, please use 'dart compile js' instead.
So not sure which of the many things I changed is ultimately the cause of this issue, which crops up when trying to build for web.
No relevant issues on the DC repo and google is being very unhelpful on this one, was hoping someone had some insight that would allow me to take the correct steps forward (or back if need be) to get around this.
TIA

Installing Vector Graphics package produces "The type or namespace 'GradientSettings' could not be found"

I'm using Unity 2019.3.0a6 and am trying to apply SVGs to game objects. I installed the Vector Graphics preview package and I see an error in the console after doing so:
Library\PackageCache\com.unity.vectorgraphics#2.0.0-preview.4\Runtime\InternalBridge\VectorImageBridge.cs(206,64): error CS0246: The type or namespace name 'GradientSettings' could not be found (are you missing a using directive or an assembly reference?)
I've googled this error in vain, as it comes up with pretty much nothing. It seems like I'm running a very recent build (June 2019) so I doubt that I need an upgrade. I've tried dragging my SVGs into the scene but I'm not able to, probably because of this error. I'm somewhat new to Unity, so if there are some logs I can check for more detailed information, please let me know.
Unity 2019.3.0a6 is an Alpha version.
Don't use alpha versions for production. They are not stable and full of bugs and errors. You should only use them for testing the absolutely newest features .. and only for that. That's the whole purpose of having alpha and beta versions.
Rather stick to the latest stable versions! Currently it is 2019.1.11

linux kernel version tag

I have an already built linux kernel image (zImage) and I want to generate the source for it.
However I'm facing trouble in that: I understand major/minor numbers meaning but I couldn't compile the same version:
target version: 4.5.0-00183-g4647b69-dirty
I even don't know the meaning of "00183-g4647b69-dirty" and how apply it.
thank in advance.
NB: I've copied the config.gz from the target kernel but in vain.
Both my own image and the other one are cross-compiled
I think you have a CONFIG_LOCALVERSION_AUTO=y. This option gets the kernel name from the "git describe" output.
In your version 4.5.0-00183-g4647b69-dirty,
"4.5.0" means the kernel version tag v4.5.0,
"00183" means you have 183 commits on top of v4.5.0
"g4647b69" means your HEAD commit SHA1 is 4647b69. (g is a prefix)
"-dirty" means you have local changes not committed to git.
What you probably need is CONFIG_LOCALVERSION=. You will be able to recreate your builds with this.

Upgrade N2CMS to latest version collected from github trunk

I am upgrading an old N2CMS website to the newest version released in the trunk (2.2.5 or something like that), following these instructions https://github.com/n2cms/n2cms/blob/master/docs/releases/upgrade_2.2.1.txt but i am getting an error when tring to compile the project:
Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
Has anyone done this before and know if there's anything else i should be doing appart from just copying files?
Thanks
Complete text of this error contains the name of DLL you are missing. Read it carefully and you will find out what DLL you need to add. It could be something like Lucene.dll which was introduced recently (it depends how old your project is).