Hello Paul,
* Paul Elliott wrote on Tue, Mar 22, 2011 at 03:01:49PM CET:
> On Tuesday, March 22, 2011 01:54:33 am Paul Elliott wrote:
> > One .c file is used as a .h file. That is, it is included by another .c
> > file and it should not be itself compiled. Why the author did this I do
> > not know
On Tuesday, March 22, 2011 01:54:33 am Paul Elliott wrote:
> I have a c library that currently uses an old style Makefile that I want to
> convert to auto*tools.
>
> One .c file is used as a .h file. That is, it is included by another .c
> file and it should not be itself compiled. Why the author
On 03/22/2011 07:54 AM, Paul Elliott wrote:
I have a c library that currently uses an old style Makefile that I want to
convert to auto*tools.
One .c file is used as a .h file. That is, it is included by another .c file and
it should not be itself compiled. Why the author did this I do not know
Paul Elliott writes:
> I have a c library that currently uses an old style Makefile that I want
> to convert to auto*tools.
> One .c file is used as a .h file. That is, it is included by another .c
> file and it should not be itself compiled. Why the author did this I do
> not know, but I do not
I have a c library that currently uses an old style Makefile that I want to
convert to auto*tools.
One .c file is used as a .h file. That is, it is included by another .c file
and
it should not be itself compiled. Why the author did this I do not know, but I
do not want to change the author's