By default GCC 7.1.1 contains -Wimplicit-fallthrough=3 in the group
-Wextra, which means that the warning can be ommitted by comment
that matches defined regular expression.
The documentation says:
> The comment needs to be followed after optional whitespace and other
comments by `case` or `default` keywords or by a user label that precedes
some `case` or `default` label.
That's why /* FALLTHRU */ occurs right above the `case` under which
the expression will fall.
GCC versions below 7 do not implement -Wimplicit-fallthrough.
Clang does not implement -Wimplicit-fallthrough for C code.
References: #268
When -std=gnu99 is used the daemon builds with errors using gcc 5.3.1
and clang 4.0.1, however no errors/warnings happen with gcc 7.1.1.
When -std=gnu11 is used, the daemon builds without errors/warnings
using gcc 7.1.1 and clang 4.0.1.
Also, the fallthrough statement was reformatted to emphasize the macro.
References: #268
Workaround unknown qmake bug on macOS at configuration stage
which happens at generation stage. Assumes Homebrew is installed.
Assumes 'qt' package by 'brew' command is installed.
References https://github.com/mattanger/ckb-next/issues/232
Workaround unknown qmake bug on macOS at configuration stage
which happens at generation stage. Assumes Homebrew is installed.
Assumes 'qt' package by 'brew' command is installed.
References https://github.com/mattanger/ckb-next/issues/232
Changes to the script:
* use Unix newlines instead of Windows' ones
* use journalctl instead of dmesg for better output control
* add current and last boot logs from kernel ring buffer
* shorten the length of a log message line
Changes to the script:
* use Unix newlines instead of Windows' ones
* use journalctl instead of dmesg for better output control
* add current and last boot logs from kernel ring buffer
* shorten the length of a log message line
ckb-dev-detect improvement
Some improvements based on suggestions from #133 and own concerns:
* don't grep for hid-generic
* add daemon info on current and last boots
In case there are multiple Qt installations, this will ensure the
application will be linked against the official Qt, which has
the default installation path in `~/Qt' and not Homebrew's Qt,
for example. This is done because of the Qt bug fixed in 5.10.
See also: #46,
https://bugreports.qt.io/browse/QTBUG-56814
The .pkgproj config is intended to be used with Packages application.
To build .pkg, `cd' into the directory where the config is and choose
Build -> Build in the upper menu. It will generate a .pkg in the root
folder.
Add uinput flag name
Knowing the proper flag name is helpful to check if you have it enabled, e.g. `grep -F CONFIG_INPUT_UINPUT /usr/src/linux/.config`
* Shorten developers' time spent on the issue
* Ease issue sorting and cathegorizing
* Make users make their homework
* Tell users precisely what developers want
Closes#110
See also: #75
Doble-clicking the quickinstall script does nothing for the author of
this commit. The script probably idles waiting for the user input or
if it doesn't, the mechanism which would guarantee a flawless execution
automatically answering Y on all the questions is broken.
A possibility to execute a new terminal window was considered, but this
is too complicated to implement because of the zoo of terminals and
their launch options on Linux.
If the argument against this is "what if the user doesn't have a working
keyboard", then the answer is "yes, but then the user still needs to
interact with the script in case of launching a new terminal window".
When the script is not launched in the terminal window, the uses sees no
output and basically cannot predict when the installation is finished.
Nevertheless, as has been already stated, the automatic execution is
broken and the user also doesn't see any output which may be useful
for him. Until it is fixed/solved, the instructions tell them to use
the terminal directly.
See also: #129
Merge branch 'testing-issue-38-SIGSEGV_when_deleting_copied_profile'
of git://github.com/frickler24/ckb-next into
frickler24-testing-issue-38-SIGSEGV_when_deleting_copied_profile
Oleksii Vilchanskyi