-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
FYI: vcpkg #1
Comments
Hi Mathis,
Also not that I finally started working on ublox-9 platform support, depending on number of required changes I'd say it will take about 2 - 4 weeks to finalize. I'll probably do it as 0.19.2 release (mostly because I want all the example cc.X.commsdsl and cc.X.generated projects to have the same major/minor versions). |
Oh yeah, thats an issue. Thanks for taking a view. I've saw the work on the feature branch. Sorry for not finishing the work on my PR last year. I had to shift my focus on other projects last year. As soon as you will update the library, I'll make a new PR at vcpkg to update 👍 |
Should I add the other mqtt libraries aswell? I've added the ublox because I don't really know any other library for the ubx protocol. Especially the new ubx-9. |
Don't think so, people usually want a MQTT client library to work with, not the protocol definition one. These protocol projects are just examples of how to use CommsChampion Ecosystem. There are heaps of other mqtt client libraries out there. I have mqtt-sn project which uses cc.mqttsn.generated and cc.mqtt311.generated protocol definitions to implement MQTT-SN client and gateway libraries. However, this project is not widely popular and not battle tested in the production environment, so I assume there will be little interest from other people to have it inside the vcpkg (or conan), at least for now. |
Also if you feel like contributing more, and you have some other open standard binary protocol that you are using in the commercial environment you can try to create the relevant cc.X.commsdsl and cc.X.generated projects yourself. Then we can put them inside the CommsChampion Ecosystem github organization. I'll assign you as owner/maintainer of these projects. |
Okay. Thanks for the feedback. I will look at how open we can be in that case. But I plan some private projects. There might be some protocols 👍 I think I will let this issue open to just post future vcpkg port updates. Or would you like to handle it differently? |
Merged the new versions. Added comms-ublox install with |
Good job, thanks |
Hi Mathis, If you want to create a pull request for this fix I recommend the following updates:
Probably the "-DCOMMSDSL_NO_WARN_AS_ERR=ON" won't be needed as well (because lack of comms_champion forced the commsdsl to get compiled without any warnings enabled), but keeping this option ON won't make much of a difference. |
Hi Alex,
thanks for letting me know.
Will update today in the evening.
…________________________________
From: Alex Robenko <[email protected]>
Sent: Friday, November 20, 2020 9:21:05 AM
To: commschamp/comms_champion <[email protected]>
Cc: Mathis Logemann <[email protected]>; Author <[email protected]>
Subject: Re: [commschamp/comms_champion] FYI: vcpkg (#13)
Hi Mathis,
Just want to let you known that I introduced some urgent hotfix (was required at my workplace) which allows to build commsdsl<https://github.com/commschamp/commsdsl> without having comms_champion<https://github.com/commschamp/comms_champion> as a dependency (see v3.5.4<https://github.com/commschamp/commsdsl/releases/tag/v3.5.4> release notes). Using the same opportunity I also introduced a fix you applied as patch in vcpkg.
If you want to create a pull request for this fix I recommend the following updates:
* Remove fix-cmake-cmakedir-path.patch
* Remove comms from the list of dependencies inside the vcpkg.json
* Update the portfile.cmake to have the following cmake options:
vcpkg_from_github(
...
REF v3.5.4
...
)
vcpkg_configure_cmake(
SOURCE_PATH ${SOURCE_PATH}
PREFER_NINJA
OPTIONS
-DCOMMSDSL_NO_COMMS_CHAMPION=ON
-DCOMMSDSL_NO_TESTS=ON
-DCOMMSDSL_NO_WARN_AS_ERR=ON # remove on next version or on next version of boost
)
Probably the "-DCOMMSDSL_NO_WARN_AS_ERR=ON" won't be needed as well (because lack of comms_champion forced the commsdsl to get compiled without and warnings enabled), but keeping this option ON won't make much of a difference.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<commschamp/comms#1>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADHNTFGDORU42TWJ4JZ4HMDSQYRHDANCNFSM4TSBHU3Q>.
|
Hi @mathisloge, |
Hi @arobenko |
updated comms_champion to 3.1.4 |
oh just saw, that new releases just came out. :D |
Hi @mathisloge, |
Hi Alex, |
Hi @mathisloge, |
Will update next week 👍 |
HI @mathisloge, By the way I support not only vcpkg, but also yocto, buildroot, and conan. |
Hi @arobenko sorry for the late response. Currently I've not so much time for my open source activities. Sorry for not working on this reliably. |
Hi Alex,
I've just updated the commschamp and commsdsl libs.
Most patches are gone now. But I needed to patch the CC_CMAKE_DIR of the commsdsl project.
microsoft/vcpkg#14521
In addition to that i've added the comms.ublox project. (the generated one)
microsoft/vcpkg#14523
It should be merged soon.
The text was updated successfully, but these errors were encountered: