This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Adding a new gcc dir


On 3/6/07, Paulo J. Matos <pocm@soton.ac.uk> wrote:
Hi all,

I've just added a new gcc subdir : head/gcc/myproj with structures and
utilities for my ipa pass which lives in head/gcc. Now I have to tell
gcc to compile the files inside myproj. Is there a standard way to do
this? I've looked into head/gcc/Makefile.in but it seem quite
cluttered and I don't really know where to begin since the gcc build
is quite complex.

Any suggestions? (Probably I can have my Makefile.in in myproj dir)
but then where should I tell gcc to compile them)


Well, added a couple of lines to gcc/Makefile.in referring to files in myproj. Still, although it is partly working one thing is annoying me. It's using these flags by default: -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute

Which means using C90, which means no mixed declarations and code, no
C++ comments, etc. Is there any way to compile at least, my files with
c99 constructs?
Or all gcc code should be built like this??

Regards,

Paulo Matos

Regards,

--
Paulo Jorge Matos - pocm at soton.ac.uk
http://www.personal.soton.ac.uk/pocm
PhD Student @ ECS
University of Southampton, UK



--
Paulo Jorge Matos - pocm at soton.ac.uk
http://www.personal.soton.ac.uk/pocm
PhD Student @ ECS
University of Southampton, UK


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]