It tells you it needs all tools built before you can use them. If your windows GOARCH is amd64, then you could “build” all required tools by running this small batch programs: set GOARCH=amd64 set GOOS=linux go tool dist install -v pkg/runtime go install -v -a std If that succeeds then you should be able … Read more
With Go 1.5 they seem to have improved the cross compilation process, meaning it is built in now. No ./make.bash-ing or brew-ing required. The process is described here but for the TLDR-ers (like me) out there: you just set the GOOS and the GOARCH environment variables and run the go build. For the even lazier … Read more
CMake can only handle one compiler at a time. So – if you don’t go the long way to set up the other compiler as a new language – you will end up with two configuration cycles. I see the following approaches to automate this process: Taking the example “CMake Cross Compiling – Using executables … Read more
As an alternative to the answer of sfstewman, here’s a small cmake (2.8) function to convert all files in a specific folder to C data and write them in wished output file: # Creates C resources file from files in given directory function(create_resources dir output) # Create empty output file file(WRITE ${output} “”) # Collect … Read more
Adding this answer partially because it fixed my problem of the same issue and so I can bookmark this question myself. I was able to fix it by doing the following: sudo apt-get install gcc-multilib g++-multilib If you’ve installed a version of gcc / g++ that doesn’t ship by default (such as g++-4.8 on lucid) … Read more
I’ve found a temporary solution by replacing the line SET(CMAKE_C_FLAGS “-std=gnu99”) by SET(CMAKE_C_FLAGS “-std=gnu99” CACHE STRING “” FORCE)
Your simplest solution is to just run CentOS 5.3 in a VM (e.g. Sun VirtualBox). This requires minimal setup, has quite reasonable overhead (assuming an Intel Mac), and you’ll be able to actually test and debug what you are building. If you really insist on cross-compiling, you must build a cross-compiler. Instructions are here and … Read more
There is a way to suppress the path translation by setting MSYS_NO_PATHCONV=1 in Windows Git MSys or MSYS2_ARG_CONV_EXCL=”*” in MSYS2. Alternatively, you can set the variable only temporarily just for that command by putting the assignment just before the command itself: MSYS_NO_PATHCONV=1 arm-none-linux-gnueabi-gcc.exe -Wall -g \ -Wl,–dynamic-linker=/usr/lib/myrpath/ld-linux.so.3 \ -Wl,-rpath=/usr/lib/myrpath \ -I../targetsysroot/usr/include \ myprogram.c -o myprogram
Just use M cross environment (MXE). It takes the pain out of the whole process: Get it: $ git clone https://github.com/mxe/mxe.git Install build dependencies Build Qt for Windows, its dependencies, and the cross-build tools; this will take about an hour on a fast machine with decent internet access; the download is about 500MB: $ cd … Read more