limitlessfx.comLimitlessFX :: Desert penguin operational facility

Skip to content You are using an outdated browser. Please upgrade your browser to improve your experience. Toggle navigation LimitlessFX Desert penguin operational facility Linux Code PHP Go Gaming World Of Warcraft Guild Wars 2 Misc Share Facebook Twitter Google Digg Reddit LinkedIn StumbleUpon Email Using the Xbox One Controller with The Talos Principle Home The Talos Principle 2016/06/30 2016/06/30 OneOfOne Leave a comment It took a bit of tinkering, but thanks to this reddit I figured it out. While this was only tested with The Talos Principle, it should work with any game that uses SDL to handle controllers. 1. Download the latest gamecontrollerdb.txt from gabomdq/SDL_GameControllerDB . 2. Add the contents of the file to an environment variable called SDL_GAMECONTROLLERCONFIG . 3. Relog and profit. Shell $ curl https://raw.githubusercontent.com/gabomdq/SDL_GameControllerDB/master/gamecontrollerdb.txt > ~/.local/gamecontrollerdb.txt $ echo 'export SDL_GAMECONTROLLERCONFIG=$(cat ~/.local/gamecontrollerdb.txt)' >> ~/.xprofile $ source ~/.xprofile && steam # or logout of your desktop and log back in. 1 2 3 $ curl https : / / raw .githubusercontent .com / gabomdq / SDL_GameControllerDB / master / gamecontrollerdb .txt > ~ / .local / gamecontrollerdb .txt $ echo 'export SDL_GAMECONTROLLERCONFIG=$(cat ~/.local/gamecontrollerdb.txt)' >> ~ / .xprofile $ source ~ / .xprofile && steam # or logout of your desktop and log back in. References: https://www.reddit.com/r/linux_gaming/comments/4mjhoe/xbox_one_controller_not_working_in_some_games / https://github.com/gabomdq/SDL_GameControllerDB http://boilingsteam.com/making-third-party-gamepads-work-with-steam-games/ controller gaming linux steam the talos principle xbox one HOWTO: Cross-compile a Go app for Windows from Linux Home Go 2014/10/09 2014/10/09 OneOfOne 3 Comments I recently needed to test some app on windows, and while cross-compiling in Go is straight-forward, the app had some C code and apparently on Arch Linux the mingw64-gcc package is misconfigured. After some head scratching I figured out a workaround until the package is fixed (task #4313 ), you have to link your Go code against ssp . note this bug is specific to Arch Linux, however other distros might build the toolchain in the same manner. Building the toolchain: 1. Download and unpack the Go source code: note this guide assumes $GOROOT is set to / usr / src / go / . Use mercurial (slow) hg clone - u release https : / / code .google .com / p / go Use the source tarball from golang.org 1a. (optional but recommended) add export PATH = "$PATH:$GOROOT/bin" to your ~ / .bashrc (or the equivalent file for your shell). 2. Compiling the native toolchain: cd $GOROOT/src $ ./make.bash ..... Installed Go for linux/amd64 in /usr/src/go-release Installed commands in /usr/src/go-release/bin 1 2 3 4 5 cd $GOROOT / src $ . / make .bash . . . . . Installed Go for linux / amd64 in / usr / src / go - release Installed commands in / usr / src / go - release / bin 3. Compiling the Windows toolchain without CGO: cd $GOROOT/src $ env GOOS=windows GOARCH=386 ./make.bash --no-clean ..... Installed Go for windows/386 in /usr/src/go-release Installed commands in /usr/src/go-release/bin 1 2 3 4 5 cd $GOROOT / src $ env GOOS = windows GOARCH = 386 . / make .bash -- no - clean . . . . . Installed Go for windows / 386 in / usr / src / go - release Installed commands in / usr / src / go - release / bin Repeat with GOARCH = amd64 if you want to build win64 binaries. 4. Compiling the Windows toolchain with CGO support: Install mingw - w64 - gcc sudo pacman -S mingw-w64-gcc ..... (1/1) installing mingw-w64-gcc 1 2 3 sudo pacman - S mingw - w64 - gcc . . . . . ( 1 / 1 ) installing mingw - w64 - gcc cd $GOROOT/src $ env CGO_ENABLED=1 GOOS=windows GOARCH=386 CC_FOR_TARGET="i686-w64-mingw32-gcc -fno-stack-protector -D_FORTIFY_SOURCE=0 -lssp" ./make.bash --no-clean ...... Installed Go for windows/386 in /usr/src/go-release Installed commands in /usr/src/go-release/bin 1 2 3 4 5 cd $GOROOT / src $ env CGO_ENABLED = 1 GOOS = windows GOARCH = 386 CC_FOR_TARGET = "i686-w64-mingw32-gcc -fno-stack-protector -D_FORTIFY_SOURCE=0 -lssp" . / make .bash -- no - clean . . . . . . Installed Go for windows / 386 in / usr / src / go - release Installed commands in / usr / src / go - release / bin Repeat with GOARCH = amd64 CC_FOR_TARGET = " x86_64 - w64 - mingw32 - gcc . . . . if you want to build win64 binaries. note that once the bug is fixed, you can remove - fno - stack - protector - D_FORTIFY_SOURCE = 0 - lssp from CC_FOR_TARGET . Actually compiling your code to run on windows: We use the same environment variables from earlier, except we have to replace CC_FOR_TARGET with CC Code: Shell package main /* static int answerToLife() { return 42; } */ import "C" import "fmt" func main() { fmt.Println("the answer to life is", C.answerToLife()) } 1 2 3 4 5 6 7 8 9 10 11 12 13 14 package main / * static int answerToLife ( ) { return 42 ; } * / import "C" import "fmt" func main ( ) { fmt .Println ( "the answer to life is" , C .answerToLife ( ) ) } Testing: $ env CGO_ENABLED=1 GOOS=windows GOARCH=386 CC="i686-w64-mingw32-gcc -fno-stack-protector -D_FORTIFY_SOURCE=0 -lssp" go build -o test32.exe $ file test32.exe test32.exe: PE32 executable (console) Intel 80386 (stripped to external PDB), for MS Windows # or build it as a GUI application so Windows won't open up a console window. $ env CGO_ENABLED=1 GOOS=windows GOARCH=386 CC="i686-w64-mingw32-gcc -fno-stack-protector -D_FORTIFY_SOURCE=0 -lssp" go build -ldflags -H=windowsgui -o test32.exe $ file test32.exe test32.exe: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for MS Windows $ wine test32.exe the answer to life is 42 1 2 3 4 5 6 7 8 9 10 11 12 $ env CGO_ENABLED = 1 GOOS = windows GOARCH = 386 CC = "i686-w64-mingw32-gcc -fno-stack-protector -D_FORTIFY_SOURCE=0 -lssp" go build - o test32 .exe $ file test32 .exe test32 .exe : PE32 executable ( console ) Intel 80386 ( stripped to external PDB ) , for MS Windows # or build it as a GUI application so Windows won't open up a console window. $ env CGO_ENABLED = 1 GOOS = windows GOARCH = 386 CC = "i686-w64-mingw32-gcc -fno-stack-protector -D_FORTIFY_SOURCE=0 -lssp" go build - ldflags - H = windowsgui - o test32 .exe $ file test32 .exe test32 .exe : PE32 executable ( GUI ) Intel 80386 ( stripped to external PDB ) , for MS Windows $ wine test32 .exe the answer to life is 42 note that to build native go with cgo you will have to use env CC = gcc go build arch-linux crosscompile howto linux windows workaround Poor man’s multi cursor in VIM Home Miscellaneous 2014/09/12 2014/09/14 OneOfOne Leave a comment I tried vim-multiple-cursors but it was just doing weird things and not replacing the right words, so after digging around for a while I came up with this: Simply add it to ~ / .vimrc . Poor man's multi cursor Vim function! PoorMultiCursor() let word = expand('<cword>') if strlen(word) > 0 call inputsave() let repl = input('replace "'.word.'" with: ') call inputrestore() if strlen(repl) > 0 execute '%s/\<'.word.'\>/'.repl.'/g' endif endif endfunction " sublime text's ctrl+d / ctrl+alt+d (find all) inoremap <C-d> <C-o>:call PoorMultiCursor()<cr> nnoremap <C-d> :call PoorMultiCursor()<cr> 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 function ! PoorMultiCursor ( ) let word = expand ( '<cword>' ) if strlen ( word ) > 0 call inputsave ( ) let repl = input ( 'replace "' . word . '" with: ' ) call inputrestore ( ) if strlen ( repl ) > 0 execute '%s/\<' . word . '\>/' . repl . '/g' endif endif endfunction " sublime text's ctrl+d / ctrl+alt+d (find all) inoremap < C - d > < C - o > : call PoorMultiCursor ( ) < cr > nnoremap < C - d > : call PoorMultiCursor ( ) < cr > Basically it's the same as using alt+f3 in Sublime Text. sublime text 3 tip vim Sourcing different environment file...