just use GHC for OSX https://ghcformacosx.github.io
the rest of these directions are preserved for historical purposes
xcode-select --install ; brew tap homebrew/versions ; brew tap homebrew/dupes \
just use GHC for OSX https://ghcformacosx.github.io
the rest of these directions are preserved for historical purposes
xcode-select --install ; brew tap homebrew/versions ; brew tap homebrew/dupes \
| ; /usr/local/bin/nasm -f macho 32.asm && ld -macosx_version_min 10.7.0 -o 32 32.o && ./32 | |
| global start | |
| section .text | |
| start: | |
| push dword msg.len | |
| push dword msg | |
| push dword 1 | |
| mov eax, 4 |
| /*http://i-skool.co.uk/mobile-development/web-design-for-mobiles-and-tablets-viewport-sizes/*/ | |
| /*At least requires the meta viewport tag with content 'width=device-width'*/ | |
| @media only screen and (max-width: 1080px) and (orientation : portrait) { | |
| /* PORTRAIT: | |
| Windows Surface Pro*/ | |
| } | |
| @media only screen and (max-width: 800px) and (orientation : portrait) { | |
| /* PORTRAIT: | |
| Acer Iconia Tab A100 |
Original link: http://www.concentric.net/~Ttwang/tech/inthash.htm
Taken from: http://web.archive.org/web/20071223173210/http://www.concentric.net/~Ttwang/tech/inthash.htm
Reformatted using pandoc
Thomas Wang, Jan 1997
last update Mar 2007
Provided that you already have a file or stream segmenter generating your .m3u8 playlist and .ts segment files (such as the ffmpeg 'hls' muxer), this little node server will serve up those files to an HLS compatible client (e.g. Safari). If you're using node for your streaming app already, this obviates the need to serve the HLS stream from a separate web server.
loosely based on https://gist.github.com/bnerd/2011232
// loosely based on https://gist.github.com/bnerd/2011232
// requires node.js >= v0.10.0
// assumes that HLS segmenter filename base is 'out'
// and that the HLS playlist and .ts files are in the current directory| Looking at the preceding token when the lexer points to a '/' | |
| character is insufficient to determine which context it's in. In | |
| fact, you need to look at an arbitrary number of preceding tokens | |
| to figure it out. This example demonstrates a case where we can | |
| pump up the number of preceding tokens to an arbitrary size | |
| before you can disambiguate your syntactic context. |
| upstream chef_server { | |
| server 127.0.0.1:4000 fail_timeout=0; | |
| } | |
| upstream chef_server_webui { | |
| server 127.0.0.1:4040 fail_timeout=0; | |
| } | |
| server { | |
| listen 443 default ssl; |