Documentation Collaboration Needed - Any programmers please get in touch with me
- Anmelden oder Registrieren um Kommentare zu schreiben
I am looking for a programmer to get in touch with me who would like to help me on a small project. I write the documentation for Trisquel on the English page. I want to write a small page on how to setup a programming environment in Trisquel. Basically it would be how to setup an IDE (Eclipse?) and get started writing or working on a small program like GNU Hello (https://www.gnu.org/s/hello/).
Unfortunately, I have tried to figure out how to do this myself but it is a little beyond me so I was wondering if someone could contact me and consult with me on the steps to set everything like eclipse, GCC, the source code up properly.
If interested you can respond here, contact me on IRC, or my contact page. Thanks!
for writing small programms like GNU Hello you really don't need Eclipse or something big like that. One of the programmers on this forum mentioned Geany once, I've been using it since and totally happy about it. It uses GCC as a backend and has three buttons: compile, build, execute. The compile button creats an .o file, so called object code. It's the program you've written, minus the libraries. Build links the libraries then and you get a nice executable in the same folder. The button execute runs that last file in a small terminal-like window.
In a nutshell, Geany rocks. It has auto completition if you try to use some class attributes or methods defined earlier. It also recognizes all the classes you made and shows them in a neat hierarchy on the left. The compiler error messages are on the bottom. Geany starts up very fast, so I assume it has a low memory footprint too (never checked that, got 2GB of RAM).
In order to start using Geany properly, you need the GCC to be installed. Try this: sudo aptitude install gcc g++ geany
.
AFAIK Eclipse has it strong side when it comes to projects that consist of many different languages. I'm only an amateur programmer myself, so stuff like that is beyond my comprehension. I work on C++ so far, nothing else.
The documentation itself isn't about writing programs like GNU hello. The goal isn't to teach a user how to program. It is to teach a user how to setup a programming environment. GNU Hello is just the program I was thinking of using. I tried geany and I am having a few issues but I may be doing something wrong.
What are the issues you are having? Setting up Eclipse is more difficult than setting up Geany. Someone sure can help you with that, but I'm having issues with Eclipse myself.
Ok well I have Geany, GNU Hello, GCC and all that stuff. Then use Geany and open hello.c and try to compile from Geany. I get this error
hello.c:19:20: fatal error: config.h: No such file or directory
I have only done one java programming class so I don't know about c programing. I know it is some sort of include but I don't know how to fix it.
You are not supposed to compile this by hand, but by using GNU autotools. There is a script called configure in the main 'hello-2.7' directory, which when run, generates a config.h file. Compilation is to be done through the make command then.
If you want to just set up a basic programming environment for beginners, then it would be better to start off with small standalone C programs.
As for the documentation, consider me in. I'll help as much as I can.
Sorry my other comment I didn't reply to yours. The one below is directed to you as well. This documentation isn't necessarily for beginners. It could be for people who already know how to program but maybe came from a non-free OS like windows and want to work on GNU projects or maybe they are a student and have only used computers where the school already setup the environment for them.
The idea kinda is that if people want to get involved with stuff like GNU they could follow this doc just to get started. I picked GNU Hello because it just seems like the classic hello world example.
How does clicking compile in a program like Geany differ from doing the ./configure; make; make install you normally do? Or can you setup something like Geany or eclipse up to use GNU autotools?
clicking compile in geany executes this (you can see that in the bottom part of geany):
g++ input.cpp output -Wall
-Wall means "warnings all", so gcc says you everything it thinks about your sluggish code, which is usually a good thing.
Executing ./configure && make && make install
is a totally different command, it uses a special make-file that has specified certain options, like what order are the source files going to be compiled in. In the end, both commands might end up addressing gcc to compile stuff, but the command using a make-file is the more sophisticated one. It is used for large projects, while the g++ command is for quickly and easily compiling one file.
Do you know if there is any way to setup Geany or Eclipse to use that make-file?
Sure, in Geany go to Build->Make | Make_Custom_Target | Make_Object | ... | Set Build commands. Those are the menu items you need to work with make files, but I'm not sure how they exactly work. Never used make files before.
Ok, I think I'm gonna ask Adherry about this. S/He said s/he would help me out with it. I've just been busy so I haven't had a chance to work on it.
Ok, I think I'm gonna ask Adherry about this. S/He said s/he would help me
out with it. I've just been busy so I haven't had a chance to work on it.
Sure, in Geany go to Build->Make | Make_Custom_Target | Make_Object | ... |
Set Build commands. Those are the menu items you need to work with make
files, but I'm not sure how they exactly work. Never used make files before.
Do you know if there is any way to setup Geany or Eclipse to use that
make-file?
clicking compile in geany executes this (you can see that in the bottom part
of geany):
g++ input.cpp output -Wall
-Wall means "warnings all", so gcc says you everything it thinks about your
sluggish code, which is usually a good thing.
Executing ./configure && make && make install is a totally different command,
it uses a special make-file that has specified certain options, like what
order are the source files going to be compiled in. In the end, both commands
might end up addressing gcc to compile stuff, but the command using a
make-file is the more sophisticated one. It is used for large projects, while
the g++ command is for quickly and easily compiling one file.
- Anmelden oder Registrieren um Kommentare zu schreiben