Addtional build info for readme.md
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 9.2k
- Forks
- 1.2k
- Avg merge
- 19m
- Merged PRs (30d)
- 4
Description
Issues like https://github.com/mattn/go-sqlite3/issues/384 related to cross compiling, i saw so many people run into it, making it clear in readme.md may be more effective.
MacOS compile for liunx 64:
- install [http://crossgcc.rts-software.org/download/gcc-4.8.1-for-linux32-linux64/gcc-4.8.1-for-linux64.dmg]gcc-4.8.1-for-linux32-linux64
- build as usual
env GOOS=linux GOARCH=amd64 CGO_ENABLED=1 CC=/usr/local/gcc-4.8.1-for-linux64/bin/x86_64-pc-linux-gcc go build
Just a thought, And other platform compiling method can be welcom ^_^
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading README.md and checking the supplied GOOS, GOARCH, CGO_ENABLED, CC, and go build example against the cross-compilation issue it references. Done means adding accurate, clear cross-compilation guidance to the README, while preserving the existing build instructions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sqlite
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100