This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
.PHONY: using-gcc using-gcc-static using-clang | |
using-gcc: | |
g++-4.8 -o main-gcc -lasan -O -g -fsanitize=address -fno-omit-frame-pointer main.cpp && \ | |
ASAN_OPTIONS=symbolize=1 ASAN_SYMBOLIZER_PATH=$(shell which llvm-symbolizer) ./main-gcc | |
using-gcc-static: | |
g++-4.8 -o main-gcc-static -static-libstdc++ -static-libasan -O -g -fsanitize=address -fno-omit-frame-pointer main.cpp && \ | |
ASAN_OPTIONS=symbolize=1 ASAN_SYMBOLIZER_PATH=$(shell which llvm-symbolizer) ./main-gcc-static |
In this tutorial, I will be explaining how to set up a simple webhook to relay your tweets to a Discord channel
- Go to https://zapier.com/ and create an account (if you don't already have one).
- Find the Discord channel in which you would like to send Tweets
Design of FHIR formats, to be honest, was essentially driven by XML and Object Oriented implementations. Not so much attention was given to design idiomatic JSON format. JSON and other JSON like formats like yaml, edn, avro are very popular in avantе-garde of programmers, some modern databases now could understad JSON as first-class data-structures, that’s why i think, good design for it is strictly required for FHIR adoption. I would like list some problems with current JSON format and propose solutions.
Done:
- Use
ccache
to speed up builds -
Document SDK installation on windows(Done by Vadi) - Add automated coverity scans
- Check Windows MinGW 5.3 issues (see Mudlet/Mudlet#1176)
- Fix technical debts:
- Correct file count for lcf
- Remove sourced-in zziplib code
- Update boost
- Install updated 7-zip (see https://www.cisecurity.org/advisory/a-vulnerability-in-7-zip-could-allow-for-arbitrary-code-execution_2018-049/)
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
import QtQuick 2.0 | |
/** | |
* adapted from StackOverflow: | |
* http://stackoverflow.com/questions/26879266/make-toast-in-android-by-qml | |
*/ | |
/** | |
* @brief An Android-like timed message text in a box that self-destroys when finished if desired | |
*/ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
------------------------------------------------------------------------------------------------------------------------------ | |
-- Module: utf8_filenames | |
------------------------------------------------------------------------------------------------------------------------------ | |
-- Filename: utf8_filenames.lua | |
-- Version: 2019-07-13 | |
-- License: MIT (see at the end of this file) | |
-- This module modifies standard Lua functions so that they work with UTF-8 filenames on Windows: | |
-- io.open | |
-- io.popen |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/usr/bin/env python3 | |
# | |
# Notarize a file (e.g. a .dmg) | |
# | |
# Usage: notarize-macos.py <Apple ID username> <Apple ID password> <file> | |
# | |
# Note: The --primary-bundle-id flag is hard-coded below, so you'll want to | |
# change that! | |
# | |
# See https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution#3087727 |
OlderNewer