dev-cpp-users Mailing List for Dev-C++ (Page 510)

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

<html><div style='background-color:'><DIV></DIV></div><br clear=all><hr>Chat with friends online, try MSN Messenger: <a href='http://g.msn.com/1HM1ENUK/c144??PS=47575'>Click Here</a><br></html>

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

> Sorry I'm so new with this. I Tried compiling myClass.cpp
> (implementation of myClass.h) and I don't get the .o file. I only
> get the .o file when I compile the userCode.cpp and the myClass.cpp
> together.

When you compile source code (.c, .cpp, etc), you receive object code
(.o). Granted, it is possible to compile and link in one step, but to
the best of my understanding, Dev-C++ compiles (makes .o files) and
links (make .exe or .dll files) in separate steps. Regardless, you
should have a file entitled "myClass.o" in the same directory as
"myClass.cpp" after you compile. If you are using the "File Open"
dialog to check for myClass.o's existence, make sure you have it set
to "All Files (*.*)" so it will show up.

> In other words, do I have to link the implementation to userCode.cpp
> in order to create the .o file?

No. The .o (object file) is made after compiling a single source code
file.

Elizabeth

Thanks I got it. Thank you very very much!

----- Original Message ----- 
From: "Elizabeth Barham" <sog...@ya...>
To: "Santiago" <sa...@ho...>
Cc: "dev-cpp-users-list" <dev...@li...>
Sent: Sunday, October 13, 2002 11:34 PM
Subject: Re: [Dev-C++] implementation .o procedure

> If you still do not understand, do this:
> 
> Make a new C project and call it "testC". Then make a new C header
> file entitled "testCheader.h" and type in:
> 
> #include <stdio.h>
> 
> int
> tester(void)
> 
> Save it.
> 
> Then make a new C source code file entitled "testCobject.c":
> 
> #include "testCheader.h"
> 
> int tester(void) {
> printf("hi.\n");
> }
> 
> Save it.
> 
> Then, in Dev-C++, push the Compile button. Provided there are no
> errors, look at the directory where testCobject.c was compiled - there
> should be a object file entitled "testCobject.o" there. That object
> file (testCobject.o) and the header file (testCheader.h) is what you
> want to share with your friends.
> 
> If you want the tutorial on how to use these, let me know.
> 
> 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
> 

Do I simply need to take my old hardware, attach a hard-drive, and 
re-install windows 95 onto it to get this to work?

David Scott Williams wrote:

> I am getting some compile errors when compiling the first 
> "TextEditorApp" example from the mini-tutorial.
>
> Basically, it is telling me that I need to define string not case 
> specific for my compiler/OS, and that I also am including an 
> unsupported toolkit (fonts.h). 
> Has  anyone had experience with this? I did post to the forum...but I 
> am unsure if the question was received or not...
>
> ~Dave
>
>
>
> -------------------------------------------------------
> 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
>

Thanks Elizabeth,
Sorry I'm so new with this. I Tried compiling myClass.cpp (implementation of
myClass.h) and I don't get the .o file. I only get the .o file when I
compile the userCode.cpp and the myClass.cpp together. In other words, do I
have to link the implementation to userCode.cpp in order to create the .o
file?

Santiago
----- Original Message -----
From: "Elizabeth Barham" <sog...@ya...>
To: "Santiago" <sa...@ho...>
Cc: "dev-cpp-users-list" <dev...@li...>
Sent: Sunday, October 13, 2002 11:27 PM
Subject: Re: [Dev-C++] implementation .o procedure

> "Santiago" <sa...@ho...> writes:
>
> > All I'd like to know is where to type:
> > gcc -c a.c
> > gcc -c b.c
> >
> > in DevC++.
>
> *You* don't, as it is in the Makefile that Dev-C++ generates (but you
> can do it if you want).
>
> You just add the object file that you want to share to the line that
> we spoke of earlier (under Project Options).
>
> What you do is write your c/c++ code that uses the shared object file,
> add the shared object file in that menu thing (under Project Options),
> then tell Dev-C++ to compile and link your project.
>
> NOW, if you want to see how to build an object file by hand, bring up
> a MS-DOS shell and cd into the directory that has the a.c file (for
> example). Then, add the directory that has gcc in it onto your path
> (consult any MS-DOS tutorial on instructions of how to do this), and
> *in the MS-DOS shell*, type in "gcc -c a.c" (or whatever your source
> file is called).
>
> *But*, Dev-C++ does this for you when you tell it to compile your
> source code, and if you look at your directory after compiling your
> code, you shall see the object file just generated. THAT OBJECT FILE
> is the one you want to share with your friends and place on that line
> in the menu thing under "Project Options".
>
> Normally, however, one makes a library with the "ar" command or a DLL.
>
> Elizabeth
>

If you still do not understand, do this:

Make a new C project and call it "testC". Then make a new C header
file entitled "testCheader.h" and type in:

#include <stdio.h>

int
tester(void)

Save it.

Then make a new C source code file entitled "testCobject.c":

#include "testCheader.h"

int tester(void) {
	printf("hi.\n");
}

Save it.

Then, in Dev-C++, push the Compile button. Provided there are no
errors, look at the directory where testCobject.c was compiled - there
should be a object file entitled "testCobject.o" there. That object
file (testCobject.o) and the header file (testCheader.h) is what you
want to share with your friends.

If you want the tutorial on how to use these, let me know.

Elizabeth

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

> All I'd like to know is where to type: 
> gcc -c a.c
> gcc -c b.c
> 
> in DevC++. 

*You* don't, as it is in the Makefile that Dev-C++ generates (but you
can do it if you want).

You just add the object file that you want to share to the line that
we spoke of earlier (under Project Options).

What you do is write your c/c++ code that uses the shared object file,
add the shared object file in that menu thing (under Project Options),
then tell Dev-C++ to compile and link your project.

NOW, if you want to see how to build an object file by hand, bring up
a MS-DOS shell and cd into the directory that has the a.c file (for
example). Then, add the directory that has gcc in it onto your path
(consult any MS-DOS tutorial on instructions of how to do this), and
*in the MS-DOS shell*, type in "gcc -c a.c" (or whatever your source
file is called).

*But*, Dev-C++ does this for you when you tell it to compile your
source code, and if you look at your directory after compiling your
code, you shall see the object file just generated. THAT OBJECT FILE
is the one you want to share with your friends and place on that line
in the menu thing under "Project Options".

Normally, however, one makes a library with the "ar" command or a DLL.

Elizabeth

All I'd like to know is where to type: 
gcc -c a.c
gcc -c b.c

in DevC++. 

After I know that, I'll have no problem with anything else.

Thanks

----- Original Message ----- 
From: "Elizabeth Barham" <sog...@ya...>
To: "Santiago" <sa...@ho...>
Cc: "dev-cpp-users-list" <dev...@li...>
Sent: Sunday, October 13, 2002 10:29 PM
Subject: Re: [Dev-C++] implementation .o procedure

> "Santiago" <sa...@ho...> writes:
> 
> > Thanks, but I guess my question is how do you put mingw in your
> > path?  I don't know how to access mingw through command, only
> > through DevC++.
> 
> But you do not need to access mingw directly to accomplish what you
> would like to do.
> 
> I do not see what was so difficult about my or others' instructions
> and if you are still having trouble I suggest you study up more on
> compiling and linking in general.
> 
> Elizabeth
> 

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

> Thanks, but I guess my question is how do you put mingw in your
> path?  I don't know how to access mingw through command, only
> through DevC++.

But you do not need to access mingw directly to accomplish what you
would like to do.

I do not see what was so difficult about my or others' instructions
and if you are still having trouble I suggest you study up more on
compiling and linking in general.

Elizabeth

Thanks, but I guess my question is how do you put mingw in your path?
I don't know how to access mingw through command, only through DevC++.

Thanks

----- Original Message -----
From: "Elizabeth Barham" <sog...@ya...>
To: "Santiago" <sa...@ho...>
Cc: "dev-cpp-users-list" <dev...@li...>
Sent: Sunday, October 13, 2002 5:05 PM
Subject: Re: [Dev-C++] implementation .o procedure

> "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
>
>
> -------------------------------------------------------
> 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
>

"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++?

Hi all,

Thanks Elizabeth, it work fine, but Im still lost.

Just work writing -lcomctl32 no points, no lib, no nothing.

I´ve tried with libcomctl32.a but did not work. Where is the hidden 
reference ?

libcomctl32.a is in the path c:\dev-cpp\lib, so can't the linker get himself without tellit -lcomctl32?

Thans again.

That is correct, -lcomctl32...

>> I found the comctl32.lib in the SDK package,  I made a empty proyect 
>> with the sample code and put in proyect linker options 
>> -l"c:/dev-cpp/lib/comctl32.lib" lib location, rebuild again, this is the 
>> building dump:
>  
>

No, not -l"c:..." but just like it says, -lcomctl32.

This adds the library "libcomctl32.a" into the link.

Elizabeth

That is correct, -lcomctl32...

>> I found the comctl32.lib in the SDK package,  I made a empty proyect 
>> with the sample code and put in proyect linker options 
>> -l"c:/dev-cpp/lib/comctl32.lib" lib location, rebuild again, this is the 
>> building dump:
>  
>

No, not -l"c:..." but just like it says, -lcomctl32.

This adds the library "libcomctl32.a" into the link.

Elizabeth

Elizabeth Barham wrote:

>Roberto Ricardi <rob...@ar...> writes:
>
>  
>
>>I tried to compile & run some sample win32 code with dev-cpp 4.9.6.1 
>>from this site: http://www.foosyerdoos.fsnet.co.uk/. Im have not 
>>experience win c++ programer so just mean trying to do know how.
>>
>>Anyone knows this example?
>>
>>//COMMON CONTROLS: DATETIME PICKER - Copyright © 2000-2002 Ken Fitlike
>>...
>>//DevC++(MinGW) must link with -lcomctl32. bcc5.5,msvc (must link with 
>>comctl32.lib)
>>#include <commctrl.h>
>>    
>>
>
>That is correct, -lcomctl32...
>
>  
>
>>I found the comctl32.lib in the SDK package,  I made a empty proyect 
>>with the sample code and put in proyect linker options 
>>-l"c:/dev-cpp/lib/comctl32.lib" lib location, rebuild again, this is the 
>>building dump:
>>    
>>
>
>No, not -l"c:..." but just like it says, -lcomctl32.
>
>This adds the library "libcomctl32.a" into the link.
>
>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
>
>  
>

The second bug is that if you change a file, compile it, and then you
undo all the changes, you see that the file has deleted all the changes,
but when you undo the last, the '*' besides the file name at the tab
disappears as it has no changes and so it shouldn't be saved, so if you
compile or save the file, it displays the file as it was when you opened
it, but it didn't save the restoring of the original code, so it is
compiling the file after the modifications.

Since my english is not perfect I'll say what it happened.
1 - Opened the project of a program which worked fine for adding a
couple of capabilities.(main.cpp = A;B;C;D)
2 - I wrote the code for that,in the main file. (*main.cpp =
A;V;B;C;D;E)
3 - Compiled, the file is saved, the asterisk disappears during
compilation (main.cpp)
4 - The program doesn't work as expected. I did not what i should do.
5 - Ctrl+z till all changes I did disappear (till it does nothing) At
first the asterisk reappears (*main.cpp), but at the last undo it
disappears again.(main.cpp=A;B;C;D)
6 - Ctrl+S Save it.
7 - Compile
8 - Run the program, it doesn't work as expected, but before it worked,
and now the code is the same.
9 - See at the code, perhaps some of the changes were left, but no, the
code is the same than when it worked fine, before my trial.
10 - Perhaps it didn't save the second time, when I undid everything. I
close Dev-Cpp.
11 - Open Dev-Cpp.
12 - See at the code, it is the original I had before starting today,
the code I compiled some days ago and worked perfectly.
13 - Compile again. Now it doesn't work, and the behavior is even worse.

14 - Shut down computer and go to sleep.
15 - Today I open Dev and see the code... it is not the code before the
work of yesterday, it is the code after the modifications (main.cpp =
A;V;B;C;D;E), when I undid and saved it didn't saved the file. Now I
undo all the changes deleting text till it is again as before
(main.cpp=A;B;C;D) and comiple and, of course, it works again.
Where, as you understood yet, A,B,C,D,E and V are symbols of the pieces
of code in main.cpp.

Regarding the other bug I reported yesterday, as vUpdate leaves the
original files with BACKUP extension, I used again Dev4.9.6.0, and when
I was opening a project of many, many files, it closed like 4.9.6.1. Now
I'm again with 4.9.6.1.

At 10.35 10/09/02 -0700, Samuel Keding wrote:
>okay,
>
>I got another one for you. I thought windows would
>create a file named LPT1 and put it in the directory
>where I ran the .exe file. It didn't. I changed the
>file name to USB1 and looked again. There was a file
>named USB1 in the same directory as my .exe file.
>When I write LPT1 though and run the .exe file, I have
>to stop the program by going through ctrl alt del.
>Nothing is ever printed, no file made, or if it is I
>don't know where it is going. I'm confused. Here is my
>source if it will help.
>...

Hello, Samuel

Try the following:
- open a Dos box
- log somewhere where you have a text file (for instance your source code)
- try to "copy" the text file on the printer ("copy foo.txt LPT1")

If the above works, then you are likely to print by opening the file named 
"LPT1" (or "PRN") and writing to it as you would do to a regular file.

I can't test the solution I'm suggesting, because I have a sort of "Windows 
printer", that is: I am allowed to print using "notepad" print command, but 
if I try to "copy" something to the printer, using a Dos box, nothing 
happens, I've been told that this is because some (cheap?) printers aren't 
smart enough and need Windows to work.

--
gisan

Hi:

I got the gtk.devpak and I got either a source package for a program
which uses it, but when I ./configure (with msys) it says that I have
not the file gtk-config, which has all the includes and links parameters
for gtk projects. I searched it, but the package has not it, so I
searched for it, but I didn't found any place where I could download it.

Somebody knows where can I find something, either how get it or how
write it? I tried something but that's not what I had to do, and I don't
know what I need provide with it (yeah, I know, includes, libs and so,
but I don't know how, and where shall I place it respect the inlcude
dirs and so).

Thanks

hi

i can't run anything by this error:

'ld C:\Dev-Cpp\proyectos\ld cannot open crt0.o: No such file or directory.'

Saludos

Federico Garcia Crespi

----------
Profesor Asociado TC, Dpto. Fisica y Arq. de computadores, Edificio=
 Torrepinet
EPS, Universidad Miguel Hernandez,  Avda. Ferrocarril s/n C.P. 03202=20
Elche  - Fax: 966658793 - Telf 966658531

----------
Un viajero esperando al autob=FAs n=BA 127 tendr=E1 que esperar, en general,=
 m=E1s=20
que otro que pueda tomar el 127 o el 19.
Esperar al primero de muchos posibles eventos es la =FAnica forma de=20
conseguir que la adquisici=F3n de computadores m=E1s r=E1pidos sea in=FAtil.

Hoare

2000	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (15)	Oct (115)	Nov (154)	Dec (258)
2001	Jan (377)	Feb (260)	Mar (249)	Apr (188)	May (152)	Jun (150)	Jul (195)	Aug (202)	Sep (200)	Oct (286)	Nov (242)	Dec (165)
2002	Jan (245)	Feb (241)	Mar (239)	Apr (346)	May (406)	Jun (369)	Jul (418)	Aug (357)	Sep (362)	Oct (597)	Nov (455)	Dec (344)
2003	Jan (446)	Feb (397)	Mar (515)	Apr (524)	May (377)	Jun (387)	Jul (532)	Aug (364)	Sep (294)	Oct (352)	Nov (295)	Dec (327)
2004	Jan (416)	Feb (318)	Mar (324)	Apr (249)	May (259)	Jun (218)	Jul (212)	Aug (259)	Sep (158)	Oct (162)	Nov (214)	Dec (169)
2005	Jan (111)	Feb (165)	Mar (199)	Apr (147)	May (131)	Jun (163)	Jul (235)	Aug (136)	Sep (84)	Oct (88)	Nov (113)	Dec (100)
2006	Jan (85)	Feb (119)	Mar (33)	Apr (31)	May (56)	Jun (68)	Jul (18)	Aug (62)	Sep (33)	Oct (55)	Nov (19)	Dec (40)
2007	Jan (22)	Feb (49)	Mar (34)	Apr (51)	May (66)	Jun (43)	Jul (116)	Aug (57)	Sep (70)	Oct (69)	Nov (97)	Dec (86)
2008	Jan (32)	Feb (47)	Mar (106)	Apr (67)	May (28)	Jun (39)	Jul (31)	Aug (25)	Sep (18)	Oct (25)	Nov (5)	Dec (21)
2009	Jan (33)	Feb (27)	Mar (27)	Apr (22)	May (22)	Jun (10)	Jul (17)	Aug (9)	Sep (21)	Oct (13)	Nov (4)	Dec (11)
2010	Jan (10)	Feb (8)	Mar (4)	Apr (1)	May	Jun (2)	Jul	Aug (1)	Sep (8)	Oct (26)	Nov (9)	Dec (1)
2011	Jan (21)	Feb (16)	Mar (4)	Apr (19)	May (26)	Jun (9)	Jul (6)	Aug	Sep (4)	Oct (3)	Nov (2)	Dec (1)
2012	Jan (4)	Feb (7)	Mar (4)	Apr	May (1)	Jun (10)	Jul (1)	Aug (1)	Sep (18)	Oct (3)	Nov (1)	Dec (1)
2013	Jan (4)	Feb (2)	Mar (15)	Apr (6)	May (1)	Jun (3)	Jul (1)	Aug (2)	Sep (4)	Oct	Nov (9)	Dec
2014	Jan (4)	Feb (1)	Mar	Apr	May	Jun	Jul (5)	Aug (4)	Sep	Oct (2)	Nov (1)	Dec (4)
2015	Jan (2)	Feb (3)	Mar (1)	Apr (2)	May (1)	Jun (2)	Jul	Aug (1)	Sep (2)	Oct (9)	Nov (35)	Dec (6)
2016	Jan (7)	Feb (10)	Mar (10)	Apr (9)	May (13)	Jun (9)	Jul (1)	Aug (3)	Sep (3)	Oct (1)	Nov (1)	Dec
2017	Jan	Feb	Mar	Apr	May	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec
2018	Jan	Feb	Mar (1)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2019	Jan (1)	Feb	Mar	Apr (2)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2020	Jan (1)	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

dev-cpp-users Mailing List for Dev-C++ (Page 510)

Open Source C & C++ IDE for Windows

dev-cpp-users — Dev-C++ users discussion list