This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Information on usage
- From: R0b0t1 <r030t1 at gmail dot com>
- To: Claudio Eterno <eterno dot claudio at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Fri, 8 Sep 2017 03:01:56 -0500
- Subject: Re: Information on usage
- Authentication-results: sourceware.org; auth=none
- References: <CA+moFQ_TvRo_Du_KzgPdkwz=B+595LjKGEv2R0tMXhOBCwojDg@mail.gmail.com>
On Thu, Sep 7, 2017 at 3:59 PM, Claudio Eterno <eterno.claudio@gmail.com> wrote:
> Hello,
> generally I work with a microcontroller that can be compiled in C by
> its specific compiler(C166 family). With this compiler it is possible
> to generate the preprocessed of a file but the output I obtain isn't
> so exaustive like gcc does when I do the same job in linux (gcc -E
> -dD...). Recently I made a test with gcc including paths of the
> C166(so the default headers, instead the linux default libs, are taken
> from the microcontroller directory). The result, apart the built-in
> defines that gcc insert(these can be easily removed with a script), is
> perfect for build a preprocessed header.
> My question: is this usage of gcc a valid use? Should I expect some traps?
> Consider this not a bug but an help request ...
> Thank you,
>
This is the GDB mailing list. You may want to ask on the GCC user
mailing list instead.
I would expect what you want to do to work, but I am slightly confused
as to why you want to do it. You may want to see if SDCC (the small
device C compiler) fits your needs. It may support C166 devices, I
can't tell for sure based on the search results I am seeing.
Cheers,
R0b0t1.