docs/gcc
Tianon Gravi e2416c1ee3 Reflow all the language stack `README-content.md` files to 80 columns and incorporate Fred's changes
This also includes Fred's updates to the `README-short.txt` files, and a bunch of very minor changes for consistency (using "PHP" instead of "php", ending sentences that describe and lead into a code block with a ":", using "Go" instead of "Golang" and "Hy" instead of "Hylang" within prose, not using periods at the end of headlines, etc).

A really fun one included here is that Java mentioned both using GNU Make inside the container (and `java` doesn't include `make` presently), and some of the prose mentioned `go build` after we ran `javac`, which was extra neat.
2014-09-13 17:33:55 -06:00
..
.keep adding some directories for andrew to dump the short and long desc in 2014-07-31 15:09:43 -06:00
README-content.md Reflow all the language stack `README-content.md` files to 80 columns and incorporate Fred's changes 2014-09-13 17:33:55 -06:00
README-short.txt Reflow all the language stack `README-content.md` files to 80 columns and incorporate Fred's changes 2014-09-13 17:33:55 -06:00
README.md Apply the footer update from fred 2014-09-11 14:56:23 -06:00
logo.png logos for all the things 2014-08-06 16:37:56 -06:00

README.md

Tags and Dockerfile links

What is gcc?

The GNU Compiler Collection (GCC) is a compiler system produced by the GNU Project supporting various programming languages. GCC is a key component of the GNU toolchain. The Free Software Foundation (FSF) distributes GCC under the GNU General Public License (GNU GPL). GCC has played an important role in the growth of free software, as both a tool and an example.

wikipedia.org/wiki/GNU_Compiler_Collection

How to use this image

Start a gcc instance running your app.

For this image, the most straight-forward use is to use a gcc container as both the build environment as well as the runtime environment. In your Dockerfile, you can do something along the lines of the following will compile and run your project.

FROM gcc:4.9
COPY . /usr/src/myapp
WORKDIR /usr/src/myapp
RUN gcc -o myapp main.c
CMD ["./myapp"]

Then run the commands to build and run the docker image.

docker build -t my-gcc-app .
docker run -it --rm --name my-running-app my-gcc-app

Compile your app inside the docker container.

It is not always appropriate to run your app inside a container. In instances where you only want to compile inside the docker instance, you can do something along the lines of the following.

docker run --rm -v "$(pwd)":/usr/src/myapp -w /usr/src/myapp gcc:4.9 gcc -o myapp myapp.c

This will add your current directory as a volume to the container, set the working directory to the volume, and run the command gcc -o myapp myapp.c which will tell gcc to compile the code in myapp.c and output the executable to myapp. Alternatively, if you have a make file, you can instead run the make command inside your container.

docker run --rm -v "$(pwd)":/usr/src/myapp -w /usr/src/myapp gcc:4.9 make

User Feedback

Issues

If you have any problems with, or questions about this image, please contact us through a GitHub issue or via the IRC channel #docker-library on Freenode.

Contributing

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.