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

Somewhere in the documentation author of Dev-C++ is claiming that
Bloodshed Dev-C++ can be used for developing commercial applications.
It is very OK :) But...

The documentation for Dev-C++ Linux states that this is a GNU project
and included GNU licence file has a very widely used statement:

> 1b) You must cause any work that you distribute or publish, that in
> whole or in part contains or is derived from the Program or any
> part thereof, to be licensed as a whole at no charge to all third
> parties under the terms of this License.

That means that Linux version is different ? Why ?
I guess Mingw32 is not implemented on Linux, am I correct ?

Regards,
Piotr



***************r-e-k-l-a-m-a**************

Masz dosc placenia prowizji bankowi ?
mBank - zaloz konto
http://epieniadze.onet.pl/mbank 

Greets, Zach.

> I have many code examples from Turbo C 2.x I want to compile in Dev-C++.
> What must I do to make these compile or what are tips/techniques to port
> the code to some Win32 compilable code?

There are probably many differences in the standards that Turbo-C implmented
and the current C++ standards that GCC 3.2/2.95 use. The <foo.h> headers are
also deprecated and GCC might refuse to compile programs using 'em
(depending on what version you have and how it's configured). Instead,
you'll have to use <cfoo> and the `using' directive. GCC will warn you about
main() not returning int, since I remember that many TC programs used simply
`main()', in place of `int main()'. Also, there are the differences in
memory-management (far-pointers, segments and offsets versus the linear
memory model). Furthermore, DOS interrupts are unavailable in Win32. And
programs that assume word-length to be equal to integer length will have
problems (in Win32, word-length is short-integer length). For BGI, I
remember reading on this list that there's a port for Windows available
called WinBGI or something. Check the archives. For programs with <conio.h>,
there's an entry in the FAQ.

That's all I can think of now. Most of the (simple) examples should be
pretty straightforward to port. Simply try to compile, and try to rectify
one error at at time.

HTH.

And people, have a safe, but otherwise chaotic, New Years'.
___________________________________________________________

Abhijit Shylanath

E-mail:   mu...@gm... || ibr...@bi...
Web-site: http://mudeth.tripod.com/

I have many code examples from Turbo C 2.x I want to compile in Dev-C++. 
What must I do to make these compile or what are tips/techniques to port 
the code to some Win32 compilable code?

I can post some sample code if you want.

Thanks and HAPPY NEW YEAR!

Zach


Zachary Uram
John 3:16
<><

That did the trick! Adding -lws2_32 to my command line is just what the
doctor ordered.

Thanks a lot for your help guys! It is greatly appreciated.

Regards,
Manoj.
http://manoj_sharma0.tripod.com


-----Original Message-----
From: Abhijit Shylanath [mailto:mu...@gm...]
Sent: Monday, December 30, 2002 5:49 AM
To: Manoj Sharma; Dev-C++
Subject: Re: [Dev-C++] Trouble compiling winsock programs.


> Hi,
>
> Thanks for your prompt responses!
>
> I should have mentioned in my earlier that I did try adding the -lwsock32
> option to the linker command line.I tried it once again though and the
> result was the same as before.The undefined reference error to WSAStartup
> error still shows up.

Try linking in the WinSock2 lib, as Charles mentioned.

> Also I would like to run this a stand alone  file (not a project). Any
> suggestions?

For this, you might want to use the command-line/make, or else, specify in
compiler options that you want the WinSock lib to be linked with all your
programs. Remove it once you're done with this project. Bit of a hassle.
Command-line would be better.

___________________________________________________________

Abhijit Shylanath

E-mail:   mu...@gm... || ibr...@bi...
Web-site: http://mudeth.tripod.com/

I have tried Dev-c++5(4.9.7.0) with gcc 2.9.5.
and after a compiled version of wxWindows that you can find in:
    http://oek-news.mnd.fh-wiesbaden.de/devc++/

and it run.

Regards,
Joan.


----- Original Message -----
From: "Goran Kavrecic" <go...@em...>
To: "DevC++" <dev...@li...>
Sent: Saturday, December 28, 2002 8:46 PM
Subject: [Dev-C++] DevC++ & wxWindows


> As a result of past years experience and current demmands I came to a
> decision to use DevC++ and wxWindows to have a multi platform development
> environment.
>
> I had some problems using DevC++.4 I added some defines(like -D__WXMSW__)
> patched some *.h files (I know it's not the supposed procedure) in order
to
> make some projects run.
>  But it become almost imposible when I came to the point of using
wxWindows.
> When if finally mannaged to compiled it failed to link(wx32.lib) It failed
> also with BCC5.5 because was no wx32.lib on the disk.
>  After that I tried to recompile wxW but failed on some parser.y file.
Then
> I gave up.
>
> I tried on W2k and later on a plain Win98. I also downloaded
DevC++5(4.9.7.0
> with gcc 3.2), but this doesn't compile even added examples. Another try
was
> Detlev Reymann's page "wxWindows and Dev-C++" - failure again (not
blaimming
> Reymann anyhow). Currently the machine has installed DevC++ 4 and 5,
Borland
> C++ 5.5, mini IDE, small IDE, VIDE, Chimera IDE, Mingw 2.0 with gcc 3.2.
>
> Anyone has some idea or procedure how to install and setup DevC++ 4
> (preferably 5) in order to work with wxW?
>
> Regards,
> Goran
>
>
>
> -------------------------------------------------------
> 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

wxwindows2.3.3 works with gcc3.2 (the official wxwindows from 
www.wxwindows.org, not the packages, I never achieved to make them 
work), and using makefiles, search in the mailing list for makeprog.g95. 
(in the message body)

Marshall Brewton wrote:

> "Goran Kavrecic" <go...@em...> wrote:
>
>> Anyone has some idea or procedure how to install and setup DevC++ 
>> 4(preferably 5) in order to work with wxW?
>>
> Hi Goran,
>
> After many hours of frustration I've come to the conclusion that the 
> default wxWindows 2.2.9 package will not work with Dev-C++ 4.7.9.x/gcc 
> 3.2.  I believe you have two choices:
>
> 1)  Use Dev-C++ 4.7.9.x/gcc 2.9.5.  A fresh installation will allow 
> for a build of the provided example.  Should you install the upgrade 
> for v4.7.9.1, be sure to copy and paste the "Compiler" flags to the 
> "C++ compiler" list box (under Project Options->Compiler->Compiler 
> Options).
>
> 2)  If you want to use the gcc 3.2 version, I could find only one 
> solution:  build a new wxWindows lib from the source provided at the 
> official wxWindows web site (located at 
> http://www.wxwindows.org/dl_msw2.htm).  This was actually a 
> frighteningly straight-forward procedure, except that that a debug 
> build of the library will not work -- an executable linked against 
> such will report a library mismatch.  I used the 2.3.4 snapshot and 
> built a Unicode release-level static lib and all appears well.  Be 
> sure to remove the existing wxWindows package and perhaps even the 
> "Image Library" package as the wxWindows source includes that for 
> libpng, libjpeg, libtiff, and libzlib.  Otherwise, watch out for lib 
> conflicts...  In addition, you'll have to perform the aforementioned 
> compiler flag copy.
>
> Good luck to you.  If you need any further help, I'll be happy to 
> provide it.
>
> Regards,
> Marshall
>
>
>
>
> -------------------------------------------------------
> 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,
>
> Thanks for your prompt responses!
>
> I should have mentioned in my earlier that I did try adding the -lwsock32
> option to the linker command line.I tried it once again though and the
> result was the same as before.The undefined reference error to WSAStartup
> error still shows up.

Try linking in the WinSock2 lib, as Charles mentioned.

> Also I would like to run this a stand alone  file (not a project). Any
> suggestions?

For this, you might want to use the command-line/make, or else, specify in
compiler options that you want the WinSock lib to be linked with all your
programs. Remove it once you're done with this project. Bit of a hassle.
Command-line would be better.

___________________________________________________________

Abhijit Shylanath

E-mail:   mu...@gm... || ibr...@bi...
Web-site: http://mudeth.tripod.com/

Thanks,
I decided for the first option because I have no preferrence regarding the
compiler.
I also thank Yeoh for his help in a direct mail.
I made it to compile an empty project.

It stopped again when I tried to compile thewxWindows samples.
I imported the MS VC Realease project of some of them but failed to link
"libz".

I've got a "libzlib.a" from DevC++4(just for a try), but got unlninked
functions (part follows):
C:/IDE/DEVCPP5/lib/libwx.a(app.o)(.text+0x447): undefined reference to
`InitCommonControls@0'
C:/IDE/DEVCPP5/lib/libwx.a(app.o)(.text+0x451): undefined reference to
`OleInitialize@4'
C:/IDE/DEVCPP5/lib/libwx.a(app.o)(.text+0x102a): undefined reference to
`OleUninitialize@0'
C:/IDE/DEVCPP5/lib/libwx.a(statbr95.o)(.text+0x3ee): undefined reference to
`CreateStatusWindowA@16'
C:/IDE/DEVCPP5/lib/libwx.a(utils.o)(.text+0x31e): undefined reference to
`WSAStartup@8'
C:/IDE/DEVCPP5/lib/libwx.a(utils.o)(.text+0x348): undefined reference to
`gethostname@8'
etc...
I probably have to link some windows specific lib. Which?

I found it strange that didn't found resources defined in wx/msw/wx.rc
I defined an prolog to absolute folder location for every resource and now
it works.
Shouldn't it get it from the include folders list?

I also upgraded to 4.7.9.1 and found some new GUI bugs there.
Does it have some side effects on compiling/linking, too?

Regards,
Goran


----- Original Message -----
From: Marshall Brewton <mlb...@ho...>
To: <dev...@li...>
Sent: Monday, December 30, 2002 12:53 AM
Subject: [Dev-C++] Re: DevC++ & wxWindows


> "Goran Kavrecic" <go...@em...> wrote:
>
> >Anyone has some idea or procedure how to install and setup DevC++
4(preferably 5) in order to work with wxW?
> >
> Hi Goran,
>
> After many hours of frustration I've come to the conclusion that the
> default wxWindows 2.2.9 package will not work with Dev-C++ 4.7.9.x/gcc
> 3.2.  I believe you have two choices:
>
> 1)  Use Dev-C++ 4.7.9.x/gcc 2.9.5.  A fresh installation will allow for
> a build of the provided example.  Should you install the upgrade for
> v4.7.9.1, be sure to copy and paste the "Compiler" flags to the "C++
> compiler" list box (under Project Options->Compiler->Compiler Options).
>
> 2)  If you want to use the gcc 3.2 version, I could find only one
> solution:  build a new wxWindows lib from the source provided at the
> official wxWindows web site (located at
> http://www.wxwindows.org/dl_msw2.htm).  This was actually a
> frighteningly straight-forward procedure, except that that a debug build
> of the library will not work -- an executable linked against such will
> report a library mismatch.  I used the 2.3.4 snapshot and built a
> Unicode release-level static lib and all appears well.  Be sure to
> remove the existing wxWindows package and perhaps even the "Image
> Library" package as the wxWindows source includes that for libpng,
> libjpeg, libtiff, and libzlib.  Otherwise, watch out for lib
> conflicts...  In addition, you'll have to perform the aforementioned
> compiler flag copy.
>
> Good luck to you.  If you need any further help, I'll be happy to
> provide it.
>
> Regards,
> Marshall
>
>
>
>
> -------------------------------------------------------
> 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

My apologies.

I wrote:

 >> a debug build of the library will not work -- an executable linked 
against such will report a library mismatch..

Adding the compiler option "-D__WXDEBUG__" to the application solves the 
problem when linking to a debug build of the wxWindows lib.

Regards,
Marshall

"Goran Kavrecic" <go...@em...> wrote:

>Anyone has some idea or procedure how to install and setup DevC++ 4(preferably 5) in order to work with wxW?
>
Hi Goran,

After many hours of frustration I've come to the conclusion that the 
default wxWindows 2.2.9 package will not work with Dev-C++ 4.7.9.x/gcc 
3.2.  I believe you have two choices:

1)  Use Dev-C++ 4.7.9.x/gcc 2.9.5.  A fresh installation will allow for 
a build of the provided example.  Should you install the upgrade for 
v4.7.9.1, be sure to copy and paste the "Compiler" flags to the "C++ 
compiler" list box (under Project Options->Compiler->Compiler Options).

2)  If you want to use the gcc 3.2 version, I could find only one 
solution:  build a new wxWindows lib from the source provided at the 
official wxWindows web site (located at 
http://www.wxwindows.org/dl_msw2.htm).  This was actually a 
frighteningly straight-forward procedure, except that that a debug build 
of the library will not work -- an executable linked against such will 
report a library mismatch.  I used the 2.3.4 snapshot and built a 
Unicode release-level static lib and all appears well.  Be sure to 
remove the existing wxWindows package and perhaps even the "Image 
Library" package as the wxWindows source includes that for libpng, 
libjpeg, libtiff, and libzlib.  Otherwise, watch out for lib 
conflicts...  In addition, you'll have to perform the aforementioned 
compiler flag copy.

Good luck to you.  If you need any further help, I'll be happy to 
provide it.

Regards,
Marshall

In the linker options, where one adds libraries, I have this:

C:/Dev-Cpp/lib/libws2_32.a

for my winsock2 projects


----- Original Message -----
From: "Manoj Sharma" <sha...@ro...>
To: "Dev-C++" <dev...@li...>
Sent: Sunday, December 29, 2002 7:13 PM
Subject: RE: [Dev-C++] Trouble compiling winsock programs.


> Hi,
>
> Thanks for your prompt responses!
>
> I should have mentioned in my earlier that I did try adding the -lwsock32
> option to the linker command line.I tried it once again though and the
> result was the same as before.The undefined reference error to WSAStartup
> error still shows up.
>
> Also I would like to run this a stand alone  file (not a project). Any
> suggestions?
> Thanks in advance once again for your help.
>
> Regards,
> Manoj.
> http://manoj_sharma0.tripod.com
>
>
> -----Original Message-----
> From: Abhijit Shylanath [mailto:mu...@gm...]
> Sent: Sunday, December 29, 2002 2:57 PM
> To: Manoj Sharma; Dev-C++
> Subject: Re: [Dev-C++] Trouble compiling winsock programs.
>
>
> Greets, Manoj.
>
> > I am trying to compile a simple winsock program using Dev-C++ and get
the
> > following error
> > [Linker error] undefined reference to WSAStartup@8. I tried generating
my
> > own libwsock32.a   library using the wsock32.dll on  my system with the
> help
> > of the dllwrap utility and linking it to my program by copying the
> generated
> > .a file to the lib directory but the error stayed the same.
>
> Just because a file is present in the `lib' directory, doesn't mean that
> it'll be linked in. You need to add it to your the list of libraries the
> linker must add. Add `-lwsock32' to the linker command-line. Any lib by
the
> name `libfoo.a' in the `lib' directory has to/can be linked in
using -lfoo.
>
> HTH.
>
> ___________________________________________________________
>
> Abhijit Shylanath
>
> E-mail:   mu...@gm... || ibr...@bi...
> Web-site: http://mudeth.tripod.com/
>
>
>
>
> -------------------------------------------------------
> 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,

Thanks for your prompt responses!

I should have mentioned in my earlier that I did try adding the -lwsock32
option to the linker command line.I tried it once again though and the
result was the same as before.The undefined reference error to WSAStartup
error still shows up.

Also I would like to run this a stand alone  file (not a project). Any
suggestions?
Thanks in advance once again for your help.

Regards,
Manoj.
http://manoj_sharma0.tripod.com


-----Original Message-----
From: Abhijit Shylanath [mailto:mu...@gm...]
Sent: Sunday, December 29, 2002 2:57 PM
To: Manoj Sharma; Dev-C++
Subject: Re: [Dev-C++] Trouble compiling winsock programs.


Greets, Manoj.

> I am trying to compile a simple winsock program using Dev-C++ and get the
> following error
> [Linker error] undefined reference to WSAStartup@8. I tried generating my
> own libwsock32.a   library using the wsock32.dll on  my system with the
help
> of the dllwrap utility and linking it to my program by copying the
generated
> .a file to the lib directory but the error stayed the same.

Just because a file is present in the `lib' directory, doesn't mean that
it'll be linked in. You need to add it to your the list of libraries the
linker must add. Add `-lwsock32' to the linker command-line. Any lib by the
name `libfoo.a' in the `lib' directory has to/can be linked in using -lfoo.

HTH.

___________________________________________________________

Abhijit Shylanath

E-mail:   mu...@gm... || ibr...@bi...
Web-site: http://mudeth.tripod.com/