RE: [Dev-C++] Convert Makefile to Dev-C++ project

[Kieran W. <Ki...@ce...>]

Hi Daniel,

I think you've just explained exactly why such a utility would be =
useful.=20

Although the Mingw and Cygwin options are both valid and in some cases =
more desirable methods, I personally believe that it would be a useful =
addition to Dev-C++ to be able to import Makefiles. This utility could =
potentially handle all Mingw specific compiler options automatically and =
address any other platform specific requirements.=20

I notice that there is a facility to import MS Visual C++ Projects.

Also some developers would just like to download Dev-C++ and load there =
existing projects (and/or Opensource projects (LibTiff, zlib, etc) into =
it. They have already done all the work of creating their Makefile, a =
simple 1 click import makefile would be useful.


> -----Original Message-----
> From: Daniel K. O. [mailto:dan...@ya...]
> Sent: 21 March 2003 16:07
> To: Louis Godio; gi...@li...; dev...@li...
> Subject: RES: [Dev-C++] Convert Makefile to Dev-C++ project
>=20
>=20
>=20
>=20
> If you want to do it with minimum effort, you can try Cygwin=20
> - almost an
> entire OS, so you'll probably just need to type './configure'=20
> and 'make'.
> Even with MSYS you can compile most of them like this.
>=20
>=20
> I compiled many GNU programs under Windows with Dev-Cpp, the=20
> task is simple:
>=20
> 1- Create a project
> 2- Add the files
> 3- Look at the Makefile for the
>  * CFLAGS/CCFLAGS/CwhateverFLAGS/every-compiler-switch and add them to
> Compiler Options
>  * LDFLAGS/LIBS/whatever-that-seems-like-linker-options and=20
> add them to
> Linker Options
> 4- If the sources need a config.h file, and you can't run the=20
> ./configure
> script, look for a "acconfig.h" (or any "*config.h") that=20
> came with the
> sources (or you can search on Google for one) and edit the #define's
> properly. Rename it to "config.h" and include it in your project.
>=20
>=20
> I don't think I would ever need a tool to convert it to a=20
> dev's project
> file; I just need
> 1- some clicks (create a project)
> 2- some more clicks (Add File -> Ctrl+A -> Open)
> 3- copy/paste from Makefile to Dev
> 4- a few key-hits (F2, "acconfig.h" -> "config.h", Add=20
> file..., edit it a
> little)
>=20
> Daniel K. O.
>=20
>=20
> It's OK to be ignorant; it's not OK to play stupid.
> http://www.catb.org/~esr/faqs/smart-questions.html
>=20
>=20
>=20
>  >  -----Mensagem original-----
>  >  De: dev...@li...
>  >  [mailto:dev...@li...]Em nome=20
> de Louis Godio
>  >  Enviada em: sexta-feira, 21 de mar=E7o de 2003 12:07
>  >  Para: gi...@li...; dev...@li...
>  >  Assunto: Re: [Dev-C++] Convert Makefile to Dev-C++ project
>  >
>  >
>  >  Hi list,
>  >  This is an important topic for those of us that want to
>  >  port GNU source code to DevC++.
>  >
>  >  GNU source code is made to compile under gcc compilers.
>  >  And all GNU source uses makefiles. But I for one spend enormous
>  >  amounts of
>  >  time trying to get GNU code to compile under DevCpp. And=20
> the problem is
>  >  almost always the GNU makefile.
>  >
>  >  If you try to ignore the GNU makefile and load the source=20
> files into
>  >  a DevC++ progect, then compile, you get tons of compile=20
> and link errors.
>  >  For example, try to compile the GNU UNSHAR code (which is=20
> a simple code
>  >  with a complex makefile).
>  >
>  >  The person asking this question, and I'm sure many other=20
> DevC++ users,
>  >  need a practical tool or solution to this makefile problem.
>  >  I'm also sure that any help, advice etc. would be greatly=20
> appreciated by
>  >  these users.


The contents of this e-mail are confidential to the ordinary user of the =
e-mail address to which it was addressed and may also be privileged.
If you are not the addressee of this e-mail you may not copy, forward, =
disclose or otherwise use it or any part of it in any form whatsoever. =20
If you have received this e-mail in error please report it to the =
postmaster at <mailto:in...@ce...>
Any views held by employees in this message do not necessarily represent =
the views and opinions of CENDRIS Limited.