Discussion:
GCC GUI???
emanu
2010-12-27 22:18:17 UTC
Permalink
Hi,

This is really not userfriendly or is it. I downloaded the aprox 60MB file
of GCC wich extracted into aprox 66000 files and how on earth should one
figure that out. No executable... where in the 4000 folders might it be? In
the Install-folder it seams to hold the pages found at
http://gcc.gnu.org/install/

Sincerely... are all thoose prerequisites and steps needed to be followed
and understood to use GCC?
Many steps contain a lot of terms and names of stuff that one is not
familiar with. Feal like I would have to be a 9-star hacker/nerd/wizard to
get thru it. Does it really have to be this hard to become introduced to
GCC?

Is there no GUI version? A version that you can actually download and
install?

I want to play with the Gravit 0.4.2 source code wich I belive has been
written in C and compiled in GCC, Make etc.

Emanuel
--
View this message in context: http://old.nabble.com/GCC-GUI----tp30541740p30541740.html
Sent from the gcc - Help mailing list archive at Nabble.com.
David Daney
2010-12-27 22:37:38 UTC
Permalink
Post by emanu
Hi,
This is really not userfriendly or is it. I downloaded the aprox 60MB file
of GCC wich extracted into aprox 66000 files and how on earth should one
figure that out. No executable... where in the 4000 folders might it be? In
the Install-folder it seams to hold the pages found at
http://gcc.gnu.org/install/
Sincerely... are all thoose prerequisites and steps needed to be followed
and understood to use GCC?
No. Those are what is needed if you wish to build GCC yourself.
Post by emanu
Many steps contain a lot of terms and names of stuff that one is not
familiar with. Feal like I would have to be a 9-star hacker/nerd/wizard to
get thru it. Does it really have to be this hard to become introduced to
GCC?
Is there no GUI version?
GCC is a command line program.
Post by emanu
A version that you can actually download and
install?
You didn't say which operating system you are using, but it is very
likely that there is a pre-built GCC that you can just install and it
will work.

Some operating systems have package management systems that will
install GCC for you. For those that do not, you can get one by
following the links on this page:

http://gcc.gnu.org/install/binaries.html
Post by emanu
I want to play with the Gravit 0.4.2 source code wich I belive has been
written in C and compiled in GCC, Make etc.
Good Luck,

David Daney
emanu
2010-12-27 23:02:15 UTC
Permalink
Post by David Daney
No. Those are what is needed if you wish to build GCC yourself.
GCC is a command line program.
Well, I didn´t wanted to compile a program to them compile another program.
I wanted a working program to compile in. And I know GCC is a command line
program but am looking for a GUI "version" of it. I've found MinGW to be
one.
(using Windows 7) I downloaded it but it wont run. Great packages. It
presents
an error message saying it misses the file: msys-1.0.dll.
--
View this message in context: http://old.nabble.com/GCC-GUI----tp30541740p30541940.html
Sent from the gcc - Help mailing list archive at Nabble.com.
Tim Prince
2010-12-27 23:54:08 UTC
Permalink
Post by emanu
Post by David Daney
No. Those are what is needed if you wish to build GCC yourself.
GCC is a command line program.
Well, I didn´t wanted to compile a program to them compile another program.
I wanted a working program to compile in. And I know GCC is a command line
program but am looking for a GUI "version" of it. I've found MinGW to be
one.
(using Windows 7) I downloaded it but it wont run. Great packages. It
presents
an error message saying it misses the file: msys-1.0.dll.
I don't know whether you're attempting to be ironic. This is the first
hint of what you apparently thought was obvious, that you wanted to run
on Windows. If you're trying to build a linux style application for
native windows, the mingw cross compilers in Cygwin might prove useful
(they were improved greatly this month), but we have no way of guessing
your "obvious" requirements. Needless to say, you could waste a lot of
time here saying you want a GUI. For that, there are several commercial
compilers, as well as the insight GUI debugger which works with gcc.
--
Tim Prince
Jonathan Wakely
2010-12-28 01:32:00 UTC
Permalink
Post by emanu
No.  Those are what is needed if you wish to build GCC yourself.
GCC is a command line program.
Well, I didn´t wanted to compile a program to them compile another program.
I wanted a working program to compile in. And I know GCC is a command line
program but am looking for a GUI "version" of it. I've found MinGW to be
one.
(using Windows 7) I downloaded it but it wont run. Great packages. It
presents
an error message saying it misses the file: msys-1.0.dll.
If you have a problem with the mingw packages, try asking on a mingw list.

Or you could search the web for "msys" which turns up this page, with
instructions on installing MSYS:
http://www.mingw.org/wiki/MSYS

As others have said, if you want to do Windows-style, GUI-driven
development, then download Windows-style, GUI-driven IDEs that include
compilers, editors etc. in one system.

If you want to use GCC and run a command-line compiler, stop
complaining on the gcc mailing lists that it's not a GUI.

And if you don't want to build GCC from source, don't download the
source package and complain that it's a lot of files, use one of the
options given at http://gcc.gnu.org/install/binaries.html
And if you have problems with those, you're better off asking for help
from those projects, not GCC.
emanu
2010-12-28 03:53:39 UTC
Permalink
Well, just forget it... I have not intentionally tryed to be ironic or
complain in a rude way about GCC in the face of GCC users and sorry if
that's how I came across. I sincerely thought that since the source code I
want to edit was mentioned having been compiled in GCC is maybe would have
to be compiled in GCC or at least that that would be the shortest way to
success. I might have mixed the concept of a program language (C) with the
concept of a tool to work with it (GCC) thinking that then there should be
command and windows style application of this GCC. Now I think I clearly
understand GCC has really "nothing to do" with the fact it has originally
been compiled in GCC and written in C. It's not a "C-program", compiled in
GCC wich for less skilled user is dificult and therefore could use the
windows style version ex MinGW of GCC. It's rather a "C-program" and there´s
a number of compilers, some command line style and among theese GCC and some
windows style ones like MinGW and really windows style ones like
Code::Blocks etc. I guess it's have not been clear enough to me even thou I
have been on GCCs site Googled on it etc. It's a lot of information and
terms etc and what I might have needed was a simple, clear explanation "for
dummies" of GCC, what it is etc. It's actually a thing I tryed to find thru
Google "GCC for Dummies". Thought I understood some of it but that I got
stuck somehow somewhere and so I thought a forum then could actually clear
things out even if sensing it might not be the truely right place for it.
Didn't have any other ideas thou. Maybe the question to have asked would
have been What is really GCC and for what do you or should you use it? But
now I think I get it enough to say it a closed/resolved matter. So sorry and
thanks.
--
View this message in context: http://old.nabble.com/GCC-GUI----tp30541740p30542871.html
Sent from the gcc - Help mailing list archive at Nabble.com.
David Brown
2010-12-28 09:08:14 UTC
Permalink
Post by emanu
Well, just forget it... I have not intentionally tryed to be ironic or
complain in a rude way about GCC in the face of GCC users and sorry if
that's how I came across. I sincerely thought that since the source code I
want to edit was mentioned having been compiled in GCC is maybe would have
to be compiled in GCC or at least that that would be the shortest way to
success. I might have mixed the concept of a program language (C) with the
concept of a tool to work with it (GCC) thinking that then there should be
command and windows style application of this GCC. Now I think I clearly
understand GCC has really "nothing to do" with the fact it has originally
been compiled in GCC and written in C. It's not a "C-program", compiled in
GCC wich for less skilled user is dificult and therefore could use the
windows style version ex MinGW of GCC. It's rather a "C-program" and there´s
a number of compilers, some command line style and among theese GCC and some
windows style ones like MinGW and really windows style ones like
Code::Blocks etc. I guess it's have not been clear enough to me even thou I
have been on GCCs site Googled on it etc. It's a lot of information and
terms etc and what I might have needed was a simple, clear explanation "for
dummies" of GCC, what it is etc. It's actually a thing I tryed to find thru
Google "GCC for Dummies". Thought I understood some of it but that I got
stuck somehow somewhere and so I thought a forum then could actually clear
things out even if sensing it might not be the truely right place for it.
Didn't have any other ideas thou. Maybe the question to have asked would
have been What is really GCC and for what do you or should you use it? But
now I think I get it enough to say it a closed/resolved matter. So sorry and
thanks.
People in this mailing list are trying to be helpful, but I believe you
have some very basic misunderstandings about gcc, compilers, gui
programs, and C. Your problems are not really about gcc or its use, and
therefore this is the wrong mailing list. But let me try to clear up
things a little here, and point you in the right direction.

You are trying to work with a program written in C (gravit). Thus you
are looking for a C compiler, and have discovered that gcc is a C compiler.

First, you have to understand what a compiler actually is. It is a
program that takes C source code, and generates machine-executable
object code. There is no such thing as a "gui" compiler, or
"windows-style" compiler - compilers are by their nature command-line
programs. They are run with various options, read some files in, and
write files out. There is no need nor use of a gui here, and no serious
compiler attempts to have such a windowed or graphics interface.

gcc is such a command line compiler.

When you download the gcc packages from the gcc website (or ftp site),
you are downloading the source code for gcc. This is of interest to
developers, package maintainers, curious hobby users, etc. It is of
little interest to end-users - they will normally want a ready-build
binary for their operating system and processor of choice.

MinGW is a an example of such a ready-built gcc binary for windows. It
is a package of ready-to-run compiler tools, libraries, and related
tools. It is often used in conjunction with msys, which is a collection
of Linux-style utilities for use on windows. Please look at the msys
and mingw websites for information about downloading and installing
these. Unfortunately, the process is not as simple as it could be - be
prepared to read a bit rather than just clicking an "install" link. If
you intend to build other open source software packages, then I
recommend you install msys as well as mingw, as a lot of software uses
the Linux-style utilities for building. Note that neither mingw nor
msys has a gui, nor are they "windows-style" programs. They are
collections of command-line programs.


The tool you are mixing up is the IDE, or "integrated development
environment". An IDE is an editor, project manager, and often debugger
that provides a front-end to a compiler. It is not a compiler itself -
it runs the compiler "in the background" as needed. The editor and the
debugger front-end are gui programs for user-interaction, while
compilation is done using the command-line compiler program, automated
by the IDE. Code::Blocks is one such IDE, available for many systems.
One choice for downloading and installing Code::Blocks on windows
includes mingw, i.e., the gcc compiler on windows. This may be your
easiest option, though it does not include the other useful utilities
from msys.


Once you believe you have your IDE and compiler in place, it is time to
try a /small/ program. Write, compile and run a "Hello world" program
before you try to go any further.


A program like "gravit" is large, and depends on a lot of other
libraries. It is not a simple matter to compile when you are unfamiliar
with the process. You may want to use simpler programs to start with.

To compile gravit, you need to install a number of other libraries. The
gravit website gives a list of these, including SDL, OpenGL and Lua.
You must first find and install these libraries for your system. You
then need to modify the makefile for gravit to get the library
installation paths right (read the instructions on the gravit website,
or in the gravit source code).

There is a google group for gravit, where you may find some help.
However, you may also be told that you should spend more time learning
the basics first, before trying to build gravit on windows.


An alternative you should consider if you are serious about learning C
development, is to switch to Linux (I recommend Linux Mint for newcomers
to Linux). Building a program like gravit is much simpler under Linux,
because all the parts (gcc, utilities, libraries) are either
pre-installed, or are easily installed from the distribution's package
manager.


I wish you luck on your quest, and hope you enjoy working with C and
gcc. Remember, it's the journey that's important, not the destination.

And if all else fails, try the pre-build gravit binary for windows:

<http://gravit.slowchop.com/dist/gravit-0.4.2-win32-installer.exe>
Dennis Clarke
2010-12-27 23:43:26 UTC
Permalink
Post by emanu
Post by David Daney
No. Those are what is needed if you wish to build GCC yourself.
GCC is a command line program.
Well, I didn´t wanted to compile a program to them compile another
program.
I wanted a working program to compile in. And I know GCC is a command line
program but am looking for a GUI "version" of it. I've found MinGW to be
one.
(using Windows 7) I downloaded it but it wont run. Great packages. It
presents
an error message saying it misses the file: msys-1.0.dll.
Perhaps it would be best to take a different approach.

Let me ask a simple question, what are you trying to do ? In as simple
terms as possible what sort of job ot task are you trying to achieve ?
--
Dennis Clarke
***@opensolaris.ca <- Email related to the open source Solaris
***@blastwave.org <- Email related to open source for Solaris
emanu
2010-12-28 04:07:27 UTC
Permalink
Post by Dennis Clarke
Perhaps it would be best to take a different approach.
Let me ask a simple question, what are you trying to do ? In as simple
terms as possible what sort of job ot task are you trying to achieve ?
Good approach to lost people, gotta understand them first. Well, as I wrote
in another answer above I think things clearing. I begin to get the basic
ideas
of modern programming languages / compilers etc. What they are and wich are
each role. Still in short to answer your question.

* I have a source code in C (.c and .h -files mainly)
* This semas to have been compiled into a program with GCC originally
* I want to edit and recompile the source the easiest way possible

I thought success to do this easily was kind of bound to GCC but am now
trying to work things out in Dev-C, Code::Blocks, MS Visual Studio Express
etc.

So matter resolved I guess, at least to GNU / GCC forums/mailing lists.

Thanks anyway.
--
View this message in context: http://old.nabble.com/GCC-GUI----tp30541740p30542902.html
Sent from the gcc - Help mailing list archive at Nabble.com.
Jonathan Wakely
2010-12-28 12:02:27 UTC
Permalink
Post by emanu
* I have a source code in C (.c and .h -files mainly)
* This semas to have been compiled into a program with GCC originally
On unix and Linux gravit probably should be compiled with gcc. The
Windows version might not be intended to be compiled with gcc. The
gravit source code includes a .dsp file and a .dsw file, which implies
that at least some Window users compile it with Visual Studio. To
find out the recommended compiler for building on Windows ask the
gravit mailing list, or switch to Linux.
Bill McEnaney
2010-12-28 15:35:58 UTC
Permalink
Post by David Brown
First, you have to understand what a compiler actually is. It is a
program that takes C source code, and generates machine-executable
object code. There is no such thing as a "gui" compiler, or
"windows-style" compiler - compilers are by their nature command-line
programs. They are run with various options, read some files in, and
write files out. There is no need nor use of a gui here, and no serious
compiler attempts to have such a windowed or graphics interface.
Please correct me if I'm wrong when I think that gcc's C compiler generates assembly language
program that as, the assembler, translates in machine language. Thanks.

Cheers,
Bill
David Brown
2010-12-28 17:45:11 UTC
Permalink
Post by Bill McEnaney
Post by David Brown
First, you have to understand what a compiler actually is. It is a
program that takes C source code, and generates machine-executable
object code. There is no such thing as a "gui" compiler, or
"windows-style" compiler - compilers are by their nature command-line
programs. They are run with various options, read some files in, and
write files out. There is no need nor use of a gui here, and no serious
compiler attempts to have such a windowed or graphics interface.
Please correct me if I'm wrong when I think that gcc's C compiler generates assembly language
program that as, the assembler, translates in machine language. Thanks.
Yes, you are correct. I was simplifying the process to make it easier
to understand. There are a number of distinct steps taken to convert
from C source code to a runable binary. Some compilers treat this all
as one process, others (such as gcc) divide it up. Most (but not all)
compilers separate the actual compilation to object code from the
linking process. Some (such as gcc) separate the compilation to
assembly code and the assembler pass. gcc also separates the
pre-processor pass from the compilation proper. And if you are using
LTO, everything then goes around in a circle. I have no doubt missed
out passes or steps that the gcc experts could fill in (such as "collect2").

But the one of the very nice features of gcc is that the gcc executable
itself acts as a driver, and hides all this messy detail from the user.
One simply calls "gcc hello.c -o hello", and gcc controls the various
programs for you. Thus you can pretend it is a single program that does
the whole job.

Continue reading on narkive:
Loading...