dev-cpp-users Mailing List for Dev-C++

"Santiago" <sa...@ho...> writes:

> Hi Elizabeth, thank you for helping me out. I still need your help creating
> the .o file with DevC++ and after I have created that file, can you explain
> what you mean by keywords "Object Files" and where to configure that. I
> could only find: "Linker options/Optional Libs or Object Files"
                                                    ^^^^^^ ^^^^^
After you compile a source file, you'll have an Object File (*.o).

Then you add that object file onto "Linker options/Optional Libs or
Object Files"

Elizabeth

Excuse my ignorance, How do you put mingw it in your path?


Thanks for your help again

Santiago

---- Original Message -----
From: "Carlos García del Monte" <cg...@wo...>
To: "dev-cpp-users-list" <dev...@li...>
Sent: Sunday, October 13, 2002 3:07 PM
Subject: Re: [Dev-C++] implementation .o procedure




Santiago escribió:

> Hi, I only have DevC++, I don't know if it's possible to use the commands
> gcc -c a.c and gcc -c b.c in DevC++. Anyway I'm still stuck with the first
> part of the process, creating a .o object file out of the implementation
of
> a class I made. These are my questions again:

Dev-C++ is the IDE for mingw, so you must be able to say gcc  -c file.c, you
only need to have it in your path.

>
> 1- How do I create an object file using the implementation I created? I
want
> someone else to use this object file so I don't have to give them my
> implementation code.

Just that, use the -c option, compile, not link. If you are speaking aboug
making one .o from various source files, that' not possible, or it shouldn't
(since the exe is done just by joining them)

>
> 2- Once the object file is created, how does the user use it to compile
> his/her own client code? how does the user refer to the file in his/her
> client code by using #include "myClass.h", or "myClass.o", or both, or
some
> other way?

#include "myClass.h", so it knows the functions used in the new code are
defined
and will found its implementation somewhere in some of the files it will
link
to. And ad myClass.o in the linker options/[...]object files tab of the
first
tab of the project options.

>
>
> I'll play class creator and main creator(user) myself using DevC++ for
> testing purposes.
>
> I'll appreciate your help!
>
> Santiago
>
> ----- Original Message -----
> From: "Elizabeth Barham" <sog...@ya...>
> To: "Santiago" <sa...@ho...>
> Sent: Monday, October 07, 2002 11:02 AM
> Subject: Re: [Dev-C++] implementation .o procedure
>
> > "Santiago" <sa...@ho...> writes:
> >
> > > Where do I add it?
> > > as an #include in *my* code?
> >
> > It is when you link the executable.
> >
> > If you have two source files, a.c and b.c, and compile them like:
> >
> > gcc -c a.c
> > gcc -c b.c
> >
> > you will have two files, a.o and b.o. Then it is a matter of linking
> > them to produce the end file:
> >
> > gcc -o test.exe a.o b.o
> >
> > The #include is in your code because that defines the interface to
> > myClass, which is all ready compiled and in object code format
> > in myClass.o.
> >
> > So to produce the executable, you'll need to do something like:
> >
> > gcc -o test.exe a.o b.o myClass.o
> >
> > In Dev-C++, you can make this occur when building using the:
> >
> > Project > Project Options
> >
> > dialog and placing "myClass.o" in the field labeled, "Linker
> > options/Optional Libs or Object Files" - the key words being "Object
> > Files" in this case (files that have the .o extension).
> >
> > Elizabeth
> >
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users

Eeps! Just what Mrs Elizabeth says.
(Didn't you prove that???????????????????????????????)



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dev-cpp-users mailing list
Dev...@li...
TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
https://lists.sourceforge.net/lists/listinfo/dev-cpp-users

Hi Elizabeth, thank you for helping me out. I still need your help creating
the .o file with DevC++ and after I have created that file, can you explain
what you mean by keywords "Object Files" and where to configure that. I
could only find: "Linker options/Optional Libs or Object Files"
Thanks again
----- Original Message -----
From: "Elizabeth Barham" <sog...@ya...>
To: "Santiago" <sa...@ho...>
Cc: "dev-cpp-users-list" <dev...@li...>
Sent: Sunday, October 13, 2002 3:41 PM
Subject: Re: [Dev-C++] implementation .o procedure


> "Santiago" <sa...@ho...> writes:
>
> > Hi, I only have DevC++, I don't know if it's possible to use the
commands
> > gcc -c a.c and gcc -c b.c in DevC++. Anyway I'm still stuck with the
first
> > part of the process, creating a .o object file out of the implementation
of
> > a class I made. These are my questions again:
> > 1- How do I create an object file using the implementation I created? I
want
> > someone else to use this object file so I don't have to give them my
> > implementation code.
> > 2- Once the object file is created, how does the user use it to compile
> > his/her own client code? how does the user refer to the file in his/her
> > client code by using #include "myClass.h", or "myClass.o", or both, or
some
> > other way?
> >
> > I'll play class creator and main creator(user) myself using DevC++ for
> > testing purposes.
> >
> > I'll appreciate your help!
>
> Normally, to do such a thing, one makes a library, which is simply a
> collection of .o files. On Win32, people tend to make DLL's, which are
> libraries that are linked in at run-time.
>
> But, anyway, just pass the .o file (the object file) to the linker
> when linking the library or executable. I explained the "menu steps"
> in the last message.
>
> > Project > Project Options
> >
> > dialog and placing "myClass.o" in the field labeled, "Linker
> > options/Optional Libs or Object Files" - the key words being "Object
> > Files" in this case (files that have the .o extension).
>
> Elizabeth
>

"Santiago" <sa...@ho...> writes:

> Hi, I only have DevC++, I don't know if it's possible to use the commands
> gcc -c a.c and gcc -c b.c in DevC++. Anyway I'm still stuck with the first
> part of the process, creating a .o object file out of the implementation of
> a class I made. These are my questions again:
> 1- How do I create an object file using the implementation I created? I want
> someone else to use this object file so I don't have to give them my
> implementation code.
> 2- Once the object file is created, how does the user use it to compile
> his/her own client code? how does the user refer to the file in his/her
> client code by using #include "myClass.h", or "myClass.o", or both, or some
> other way?
> 
> I'll play class creator and main creator(user) myself using DevC++ for
> testing purposes.
> 
> I'll appreciate your help!

Normally, to do such a thing, one makes a library, which is simply a
collection of .o files. On Win32, people tend to make DLL's, which are
libraries that are linked in at run-time.

But, anyway, just pass the .o file (the object file) to the linker
when linking the library or executable. I explained the "menu steps"
in the last message.

> Project > Project Options
>
> dialog and placing "myClass.o" in the field labeled, "Linker
> options/Optional Libs or Object Files" - the key words being "Object
> Files" in this case (files that have the .o extension).

Elizabeth

Santiago escribi=F3:

> Hi, I only have DevC++, I don't know if it's possible to use the comman=
ds
> gcc -c a.c and gcc -c b.c in DevC++. Anyway I'm still stuck with the fi=
rst
> part of the process, creating a .o object file out of the implementatio=
n of
> a class I made. These are my questions again:

Dev-C++ is the IDE for mingw, so you must be able to say gcc  -c file.c, =
you
only need to have it in your path.

>
> 1- How do I create an object file using the implementation I created? I=
 want
> someone else to use this object file so I don't have to give them my
> implementation code.

Just that, use the -c option, compile, not link. If you are speaking abou=
g
making one .o from various source files, that' not possible, or it should=
n't
(since the exe is done just by joining them)

>
> 2- Once the object file is created, how does the user use it to compile
> his/her own client code? how does the user refer to the file in his/her
> client code by using #include "myClass.h", or "myClass.o", or both, or =
some
> other way?

#include "myClass.h", so it knows the functions used in the new code are =
defined
and will found its implementation somewhere in some of the files it will =
link
to. And ad myClass.o in the linker options/[...]object files tab of the f=
irst
tab of the project options.

>
>
> I'll play class creator and main creator(user) myself using DevC++ for
> testing purposes.
>
> I'll appreciate your help!
>
> Santiago
>
> ----- Original Message -----
> From: "Elizabeth Barham" <sog...@ya...>
> To: "Santiago" <sa...@ho...>
> Sent: Monday, October 07, 2002 11:02 AM
> Subject: Re: [Dev-C++] implementation .o procedure
>
> > "Santiago" <sa...@ho...> writes:
> >
> > > Where do I add it?
> > > as an #include in *my* code?
> >
> > It is when you link the executable.
> >
> > If you have two source files, a.c and b.c, and compile them like:
> >
> > gcc -c a.c
> > gcc -c b.c
> >
> > you will have two files, a.o and b.o. Then it is a matter of linking
> > them to produce the end file:
> >
> > gcc -o test.exe a.o b.o
> >
> > The #include is in your code because that defines the interface to
> > myClass, which is all ready compiled and in object code format
> > in myClass.o.
> >
> > So to produce the executable, you'll need to do something like:
> >
> > gcc -o test.exe a.o b.o myClass.o
> >
> > In Dev-C++, you can make this occur when building using the:
> >
> > Project > Project Options
> >
> > dialog and placing "myClass.o" in the field labeled, "Linker
> > options/Optional Libs or Object Files" - the key words being "Object
> > Files" in this case (files that have the .o extension).
> >
> > Elizabeth
> >
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users

Eeps! Just what Mrs Elizabeth says.
(Didn't you prove that???????????????????????????????)

Hi, I only have DevC++, I don't know if it's possible to use the commands
gcc -c a.c and gcc -c b.c in DevC++. Anyway I'm still stuck with the first
part of the process, creating a .o object file out of the implementation of
a class I made. These are my questions again:
1- How do I create an object file using the implementation I created? I want
someone else to use this object file so I don't have to give them my
implementation code.
2- Once the object file is created, how does the user use it to compile
his/her own client code? how does the user refer to the file in his/her
client code by using #include "myClass.h", or "myClass.o", or both, or some
other way?

I'll play class creator and main creator(user) myself using DevC++ for
testing purposes.

I'll appreciate your help!

Santiago


----- Original Message -----
From: "Elizabeth Barham" <sog...@ya...>
To: "Santiago" <sa...@ho...>
Sent: Monday, October 07, 2002 11:02 AM
Subject: Re: [Dev-C++] implementation .o procedure


> "Santiago" <sa...@ho...> writes:
>
> > Where do I add it?
> > as an #include in *my* code?
>
> It is when you link the executable.
>
> If you have two source files, a.c and b.c, and compile them like:
>
> gcc -c a.c
> gcc -c b.c
>
> you will have two files, a.o and b.o. Then it is a matter of linking
> them to produce the end file:
>
> gcc -o test.exe a.o b.o
>
> The #include is in your code because that defines the interface to
> myClass, which is all ready compiled and in object code format
> in myClass.o.
>
> So to produce the executable, you'll need to do something like:
>
> gcc -o test.exe a.o b.o myClass.o
>
> In Dev-C++, you can make this occur when building using the:
>
> Project > Project Options
>
> dialog and placing "myClass.o" in the field labeled, "Linker
> options/Optional Libs or Object Files" - the key words being "Object
> Files" in this case (files that have the .o extension).
>
> Elizabeth
>

I don't think there's a way. I used to use that feature a lot on turbo c++.
I think that is the only important (not to mention simple) missing feature
in devC++.

----- Original Message -----
From: "Eric Richards" <e.r...@pa...>
To: "Dev-C++ -Users-List" <dev...@li...>
Sent: Sunday, October 13, 2002 3:04 AM
Subject: RE: [Dev-C++] Step-by-step and variable inspection


> THANK you very much Macário
>
>
> Your email has prompted me have oneeeeeeeeee ............ more go at
getting
> the help files, now I should be able get moving with it.   and the first
> thing I will try is a program and run it step by step.
>
>
> From Eric
>
> NO ATTACHMENT WAS SENT WITH THIS EMAIL,
>  IF THERE IS ONE, IT IS A UNDETECTED VIRUS,  PLEASE LET ME KNOW..
>
>
>
> -----Original Message-----
> From: dev...@li...
> [mailto:dev...@li...]On Behalf Of Eric
> Richards
> Sent: Sunday, October 13, 2002 7:38 PM
> To: Dev-C++ -Users-List
> Subject: RE: [Dev-C++] Step-by-step and variable inspection
>
>
> I have no idea how too help you, I have repeatedly asked the group how to
> get the help files and never been given helpful answer,
>
>
>
>
> From Eric
>
>
> -----Original Message-----
> From: dev...@li...
> [mailto:dev...@li...]On Behalf Of André
> Macário Barros
> Sent: Sunday, October 13, 2002 7:36 PM
> To: dev...@li...
> Subject: [Dev-C++] Step-by-step and variable inspection
>
>
> Does anybody know how to execute a step-by-step (F7 and F8 Turbo C like)
> program in Dev-C++?
>
>
>
> -------------------------------------------------------
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.401 / Virus Database: 226 - Release Date: 10/9/02
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>

THANK you very much Macário


Your email has prompted me have oneeeeeeeeee ............ more go at getting
the help files, now I should be able get moving with it.   and the first
thing I will try is a program and run it step by step.


From Eric

NO ATTACHMENT WAS SENT WITH THIS EMAIL,
 IF THERE IS ONE, IT IS A UNDETECTED VIRUS,  PLEASE LET ME KNOW..



-----Original Message-----
From: dev...@li...
[mailto:dev...@li...]On Behalf Of Eric
Richards
Sent: Sunday, October 13, 2002 7:38 PM
To: Dev-C++ -Users-List
Subject: RE: [Dev-C++] Step-by-step and variable inspection


I have no idea how too help you, I have repeatedly asked the group how to
get the help files and never been given helpful answer,




From Eric


-----Original Message-----
From: dev...@li...
[mailto:dev...@li...]On Behalf Of André
Macário Barros
Sent: Sunday, October 13, 2002 7:36 PM
To: dev...@li...
Subject: [Dev-C++] Step-by-step and variable inspection


Does anybody know how to execute a step-by-step (F7 and F8 Turbo C like)
program in Dev-C++?



-------------------------------------------------------


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.401 / Virus Database: 226 - Release Date: 10/9/02

I have no idea how too help you, I have repeatedly asked the group how to
get the help files and never been given helpful answer,




From Eric


NO ATTACHMENT WAS SENT WITH THIS EMAIL,
 IF THERE IS ONE, IT IS A UNDETECTED VIRUS,  PLEASE LET ME KNOW..





-----Original Message-----
From: dev...@li...
[mailto:dev...@li...]On Behalf Of André
Macário Barros
Sent: Sunday, October 13, 2002 7:36 PM
To: dev...@li...
Subject: [Dev-C++] Step-by-step and variable inspection


Does anybody know how to execute a step-by-step (F7 and F8 Turbo C like)
program in Dev-C++?



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dev-cpp-users mailing list
Dev...@li...
TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
https://lists.sourceforge.net/lists/listinfo/dev-cpp-users

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.401 / Virus Database: 226 - Release Date: 10/9/02

Does anybody know how to execute a step-by-step (F7 and F8 Turbo C like)
program in Dev-C++?