Re: [Kicad-developers] Linux Packaging heads up
On my side (ppa Ubuntu) I see an impact on the nightly builds package since I produce renamed desktop files. I'll check that point as soon as possible. Le mer. 20 janv. 2021 à 18:35, Seth Hillbrand a écrit : > This is a heads up for our Linux packagers that the launcher locations > have changed in the master branch. > > You will now find the .desktop launcher files in the build directory, > under `resources/linux/launchers/` > > -Seth > > -- > [image: KiCad Services Corporation Logo] > Seth Hillbrand > *Lead Developer* > +1-530-302-5483 > Long Beach, CA > www.kipro-pcb.comi...@kipro-pcb.com > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Odp: Re: Questions to the QA code
Hi Jeff, Did you use github.com github.com or that one for Java github.com github.com ? Mockitopp has its last code update about ~1,5 year ago, so it looks it has the same downside as HippoMocks. There is also Mockpp, also not actively developed: sourceforge.net sourceforge.net BR, SK Dnia 17 stycznia 2021 16:45 Jeff Young j...@rokeby.ie napisał(a): I’ve used Mockito. Can’t say I remember a thing about it, though (which could be good?). Cheers, Jeff. On 17 Jan 2021, at 14:49, Sylwester Kocjan s.koc...@o2.pl wrote: Hello, On 17/01/2021 09:47, Alex wrote: ...GTest, Doctest and Catch2, (...) theyll all get the job done They are all testing frameworks without mocking capability. We have already Boost.Test based tests and I find it unnecessary effort to migrate them, and alone they dont solve the problem. On 17/01/2021 09:47, Alex wrote:I wasnt aware that GMock could operate separately from GTest, but if it can, thats pretty neat. On Sun, Jan 17, 2021, 12:15 AM Andrew Lutsenko anlutse...@gmail.com wrote:You can also use gmock separately from gtest. Since some time gmock is a part of gtest. Any search results in the topic of gmock with another testing frameworks are quite old. I think there is a risk that it will not work. On 17/01/2021 09:47, Alex wrote:Catch is a single header I was instructed to avoid introducing new dependencies, hence my initial choice of single-header HippoMocks: gitlab.com gitlab.com On Sat, Jan 16, 2021 at 6:47 AM Seth Hillbrand s...@kipro-pcb.com wrote:The downside of HippoMocks from what I can gather is that the project appears abandoned. Sadly, this is true. There are also other choices, but I dont have any hands-on experience with them and I dont know which one to choose: - turtle.sourceforge.net turtle.sourceforge.net - github.com github.com - github.com github.com Best regards, Sylwester On 17/01/2021 09:47, Alex wrote: Ive used GTest, Doctest and Catch2, and theyll all get the job done; Doctest is definitely the fastest to compile, but also has the least of features; Catch and GTest have the most features. I wasnt aware that GMock could operate separately from GTest, but if it can, thats pretty neat. I believe Doctest and Catch both are single header - I know at least Catch is a single header; but I think it makes sense to use a git submodule in this case.On Sun, Jan 17, 2021, 12:15 AM Andrew Lutsenkoanlutse...@gmail.com wrote: I would also suggest to look towards gtest/gmock. Its widely adopted, works with cmake out of the box, has integrations with popular IDEs and a good choice of supporting tools like parallelized runners, GUI inspectors etc. You can also use gmock separately from gtest. Andrew On Sat, Jan 16, 2021 at 6:47 AM Seth Hillbrands...@kipro-pcb.com wrote: Hi Sylwester- I havent used HippoMocks but in general, adding QA tests is always welcome as long as they run as expected under the Fedora docker we use for online QA with GitLab. The downside of HippoMocks from what I can gather is that the project appears abandoned. If Im incorrect here, can you link to the current repository/documentation? Thanks- Seth On Fri, Jan 15, 2021 at 2:49 PM Sylwester Kocjans.koc...@o2.pl wrote: Hello, I have two questions regarding QA code for KiCad and Id like to ask for your comments about them: 1. I reviewed contents of qa directory in KiCad repo and I saw some issues that can be fixed. Could you please take a look at the summary and let me know if they are valid: docs.google.com docs.google.com 2. What do you think about adding mocking library to the KiCad code? I found that PGM object is mocked few times gitlab.com gitlab.com A libary for creating mocks would simplify creting the tests. In this MR and commit: gitlab.com gitlab.com gitlab.com gitlab.com there is added HippoMocks, a single-header mocking tool and it does its job. If thats ok, it could help to get rid of these duplicated mocks (maybe even hand-written mocks at all). Best regards, Sylwester __ Mailing list: launchpad.net launchpad.net
Re: [Kicad-developers] Linux Packaging heads up
You are correct, Nick. No changes are needed. The "make install" step copies
the files from linux/launchers into share/applications and the spec file picks them up
from there.
Steve
On 1/20/21 3:22 PM, Steven A. Falco wrote:
The kicad.spec file for Fedora runs desktop-file-install on the desktop files.
It will likely have to change. I'm running a test build now. Here is the
relevant code from the spec file:
# Desktop integration
for desktopfile in %{buildroot}%{_datadir}/applications/*.desktop ; do
desktop-file-install \
--dir %{buildroot}%{_datadir}/applications \
--remove-category Development \
--delete-original \
${desktopfile}
done
Steve
On 1/20/21 3:15 PM, Nick Østergaard wrote:
Mmm, I guess they are also part of the install target in cmake and no real
packaging changes are needed a such, right?
On Wed, 20 Jan 2021 at 18:34, Seth Hillbrand mailto:s...@kipro-pcb.com>> wrote:
This is a heads up for our Linux packagers that the launcher locations have
changed in the master branch.
You will now find the .desktop launcher files in the build directory, under
`resources/linux/launchers/`
-Seth
-- KiCad Services Corporation Logo
Seth Hillbrand
*Lead Developer*
+1-530-302-5483
Long Beach, CA
www.kipro-pcb.com
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Linux Packaging heads up
The kicad.spec file for Fedora runs desktop-file-install on the desktop files.
It will likely have to change. I'm running a test build now. Here is the
relevant code from the spec file:
# Desktop integration
for desktopfile in %{buildroot}%{_datadir}/applications/*.desktop ; do
desktop-file-install \
--dir %{buildroot}%{_datadir}/applications \
--remove-category Development \
--delete-original \
${desktopfile}
done
Steve
On 1/20/21 3:15 PM, Nick Østergaard wrote:
Mmm, I guess they are also part of the install target in cmake and no real
packaging changes are needed a such, right?
On Wed, 20 Jan 2021 at 18:34, Seth Hillbrand mailto:s...@kipro-pcb.com>> wrote:
This is a heads up for our Linux packagers that the launcher locations have
changed in the master branch.
You will now find the .desktop launcher files in the build directory, under
`resources/linux/launchers/`
-Seth
--
KiCad Services Corporation Logo
Seth Hillbrand
*Lead Developer*
+1-530-302-5483
Long Beach, CA
www.kipro-pcb.com
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Linux Packaging heads up
Mmm, I guess they are also part of the install target in cmake and no real packaging changes are needed a such, right? On Wed, 20 Jan 2021 at 18:34, Seth Hillbrand wrote: > This is a heads up for our Linux packagers that the launcher locations > have changed in the master branch. > > You will now find the .desktop launcher files in the build directory, > under `resources/linux/launchers/` > > -Seth > > -- > [image: KiCad Services Corporation Logo] > Seth Hillbrand > *Lead Developer* > +1-530-302-5483 > Long Beach, CA > www.kipro-pcb.comi...@kipro-pcb.com > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Linux Packaging heads up
This is a heads up for our Linux packagers that the launcher locations have changed in the master branch. You will now find the .desktop launcher files in the build directory, under `resources/linux/launchers/` -Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
