dev-cpp-users

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.

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

[Per W. <pw...@ia...>]

Note that the Visual C++ projects are using a fixed-format file, while a
makefile may contain just about anything that will execute. In short, the
makefile may contain constructs that are not possible to represent in the
Dev-Cpp project files - and having the Dev-Cpp project just fork out a
make run wouldn't be a solution if the machine isn't configured to be able
to run make natively anyway.

/Per W

On Fri, 21 Mar 2003, Kieran Walshe wrote:

> Hi Daniel,
>
> I think you've just explained exactly why such a utility would be useful.
>
> Although the Mingw and Cygwin options are both valid and in some cases mo=
re desirable methods, I personally believe that it would be a useful additi=
on to Dev-C++ to be able to import Makefiles. This utility could potentiall=
y handle all Mingw specific compiler options automatically and address any =
other platform specific requirements.
>
> 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 e=
xisting 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
> >
> >
> >
> >
> > If you want to do it with minimum effort, you can try Cygwin
> > - almost an
> > entire OS, so you'll probably just need to type './configure'
> > and 'make'.
> > Even with MSYS you can compile most of them like this.
> >
> >
> > I compiled many GNU programs under Windows with Dev-Cpp, the
> > task is simple:
> >
> > 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
> > add them to
> > Linker Options
> > 4- If the sources need a config.h file, and you can't run the
> > ./configure
> > script, look for a "acconfig.h" (or any "*config.h") that
> > 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.
> >
> >
> > I don't think I would ever need a tool to convert it to a
> > 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
> > file..., edit it a
> > little)
> >
> > Daniel K. O.
> >
> >
> > It's OK to be ignorant; it's not OK to play stupid.
> > http://www.catb.org/~esr/faqs/smart-questions.html
> >
> >
> >
> >  >  -----Mensagem original-----
> >  >  De: dev...@li...
> >  >  [mailto:dev...@li...]Em nome
> > 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
> > the problem is
> >  >  almost always the GNU makefile.
> >  >
> >  >  If you try to ignore the GNU makefile and load the source
> > files into
> >  >  a DevC++ progect, then compile, you get tons of compile
> > and link errors.
> >  >  For example, try to compile the GNU UNSHAR code (which is
> > a simple code
> >  >  with a complex makefile).
> >  >
> >  >  The person asking this question, and I'm sure many other
> > DevC++ users,
> >  >  need a practical tool or solution to this makefile problem.
> >  >  I'm also sure that any help, advice etc. would be greatly
> > 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, di=
sclose or otherwise use it or any part of it in any form whatsoever.
> If you have received this e-mail in error please report it to the postmas=
ter at <mailto:in...@ce...>
> Any views held by employees in this message do not necessarily represent =
the views and opinions of CENDRIS Limited.
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:Crypto Challenge is now open!
> Get cracking and register here for some mind boggling fun and
> the chance of winning an Apple iPod:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> _______________________________________________
> 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
>

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

[Louis G. <lg...@ya...>]

Per,

What about a tool that only translates makefiles to .dev
files for a limited number of of constructs ?
A tool that only translates the constructs
outlined in Daniel K. O. note would still be a great addition to
DevCpp.




--- Per Westermark <pw...@ia...> wrote:
> Note that the Visual C++ projects are using a fixed-format file, while a
> makefile may contain just about anything that will execute. In short,
> the
> makefile may contain constructs that are not possible to represent in
> the
> Dev-Cpp project files - and having the Dev-Cpp project just fork out a
> make run wouldn't be a solution if the machine isn't configured to be
> able
> to run make natively anyway.
> 
> /Per W
> 
> On Fri, 21 Mar 2003, Kieran Walshe wrote:
> 
> > Hi Daniel,
> >
> > I think you've just explained exactly why such a utility would be
> useful.
> >
> > 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.
> >
> > 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
> > >
> > >
> > >
> > >
> > > If you want to do it with minimum effort, you can try Cygwin
> > > - almost an
> > > entire OS, so you'll probably just need to type './configure'
> > > and 'make'.
> > > Even with MSYS you can compile most of them like this.
> > >
> > >
> > > I compiled many GNU programs under Windows with Dev-Cpp, the
> > > task is simple:
> > >
> > > 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
> > > add them to
> > > Linker Options
> > > 4- If the sources need a config.h file, and you can't run the
> > > ./configure
> > > script, look for a "acconfig.h" (or any "*config.h") that
> > > 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.
> > >
> > >
> > > I don't think I would ever need a tool to convert it to a
> > > 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
> > > file..., edit it a
> > > little)
> > >
> > > Daniel K. O.
> > >
> > >
> > > It's OK to be ignorant; it's not OK to play stupid.
> > > http://www.catb.org/~esr/faqs/smart-questions.html
> > >
> > >
> > >
> > >  >  -----Mensagem original-----
> > >  >  De: dev...@li...
> > >  >  [mailto:dev...@li...]Em nome
> > > de Louis Godio
> > >  >  Enviada em: sexta-feira, 21 de março 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
> > > the problem is
> > >  >  almost always the GNU makefile.
> > >  >
> > >  >  If you try to ignore the GNU makefile and load the source
> > > files into
> > >  >  a DevC++ progect, then compile, you get tons of compile
> > > and link errors.
> > >  >  For example, try to compile the GNU UNSHAR code (which is
> > > a simple code
> > >  >  with a complex makefile).
> > >  >
> > >  >  The person asking this question, and I'm sure many other
> > > DevC++ users,
> > >  >  need a practical tool or solution to this makefile problem.
> > >  >  I'm also sure that any help, advice etc. would be greatly
> > > 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.
> > 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.
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by:Crypto Challenge is now open!
> > Get cracking and register here for some mind boggling fun and
> > the chance of winning an Apple iPod:
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> > _______________________________________________
> > 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 you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com

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

[Per W. <pw...@ia...>]

Note that Daniel's example contained a number of logical wild-cards,
especially about figuring out flags etc. An import function would need to
parse the $xx functions/declarations of the makefile, to get the true
values of any flags.

I would almost think that the easist way to do it is to either pick up the
real source code of the make program - or run make and capture the output
of 'make -n', to get the correct macro expansions.

For each gcc -c xx.o xx.c, you would get one c file to add to the project,
together with the flags needed to compile it.

In the same way, you would get the link flags.

What to do if the makefile runs anything bug compiler, linker, librarian?
Should cp, mv, rm, ... be translated to corresponding Win32 cmd actions
run in before/after rules?

Note that the concept wouldn't handle makefiles that needs ./configure to
be run first.

/Per W

On Fri, 21 Mar 2003, Louis Godio wrote:

> Per,
>
> What about a tool that only translates makefiles to .dev
> files for a limited number of of constructs ?
> A tool that only translates the constructs
> outlined in Daniel K. O. note would still be a great addition to
> DevCpp.
>
>
>
>
> --- Per Westermark <pw...@ia...> wrote:
> > Note that the Visual C++ projects are using a fixed-format file, while =
a
> > makefile may contain just about anything that will execute. In short,
> > the
> > makefile may contain constructs that are not possible to represent in
> > the
> > Dev-Cpp project files - and having the Dev-Cpp project just fork out a
> > make run wouldn't be a solution if the machine isn't configured to be
> > able
> > to run make natively anyway.
> >
> > /Per W
> >
> > On Fri, 21 Mar 2003, Kieran Walshe wrote:
> >
> > > Hi Daniel,
> > >
> > > I think you've just explained exactly why such a utility would be
> > useful.
> > >
> > > Although the Mingw and Cygwin options are both valid and in some case=
s
> > 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 an=
d
> > address any other platform specific requirements.
> > >
> > > 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
> > > >
> > > >
> > > >
> > > >
> > > > If you want to do it with minimum effort, you can try Cygwin
> > > > - almost an
> > > > entire OS, so you'll probably just need to type './configure'
> > > > and 'make'.
> > > > Even with MSYS you can compile most of them like this.
> > > >
> > > >
> > > > I compiled many GNU programs under Windows with Dev-Cpp, the
> > > > task is simple:
> > > >
> > > > 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
> > > > add them to
> > > > Linker Options
> > > > 4- If the sources need a config.h file, and you can't run the
> > > > ./configure
> > > > script, look for a "acconfig.h" (or any "*config.h") that
> > > > 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.
> > > >
> > > >
> > > > I don't think I would ever need a tool to convert it to a
> > > > 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
> > > > file..., edit it a
> > > > little)
> > > >
> > > > Daniel K. O.
> > > >
> > > >
> > > > It's OK to be ignorant; it's not OK to play stupid.
> > > > http://www.catb.org/~esr/faqs/smart-questions.html
> > > >
> > > >
> > > >
> > > >  >  -----Mensagem original-----
> > > >  >  De: dev...@li...
> > > >  >  [mailto:dev...@li...]Em nome
> > > > 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
> > > > the problem is
> > > >  >  almost always the GNU makefile.
> > > >  >
> > > >  >  If you try to ignore the GNU makefile and load the source
> > > > files into
> > > >  >  a DevC++ progect, then compile, you get tons of compile
> > > > and link errors.
> > > >  >  For example, try to compile the GNU UNSHAR code (which is
> > > > a simple code
> > > >  >  with a complex makefile).
> > > >  >
> > > >  >  The person asking this question, and I'm sure many other
> > > > DevC++ users,
> > > >  >  need a practical tool or solution to this makefile problem.
> > > >  >  I'm also sure that any help, advice etc. would be greatly
> > > > 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=
=2E
> > > 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.
> > > 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.
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by:Crypto Challenge is now open!
> > > Get cracking and register here for some mind boggling fun and
> > > the chance of winning an Apple iPod:
> > > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> > > _______________________________________________
> > > 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 you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com
>

[Dev-C++] [OT] - mail policy [was: Convert Makefile to Dev-C++ project]

[Luigi S. <gi...@li...>]

Hi guys,

I understand that being part of this thread on makefiles, you want to keep me
up-to-date with all messages, but remember: as a member of the list
I get a copy of the messages which you send to the list; so, if you also
add me to the "To" field or the "Cc" field, I'll get an extra copy ;-)

Couldn't you explain your mail client that you wish to reply to the list
only?

Thank you
-- 
>> gisan >>